feat: #2367 add MCP tool meta resolver support #2375
+317
−57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request resolves #2367
Here is a documentation draft:
If you need to attach MCP request metadata to tool calls, supply a
tool_meta_resolverwhen constructing the server. The resolver receives an [MCPToolMetaContext][agents.mcp.MCPToolMetaContext] and returns a dict that is sent as MCP_meta.Notes:
MCPUtil.invoke_mcp_tool, it is merged over the resolver output.list_tools()does not accept metadata in the MCP Python SDK yet.server.call_tooldirectly, passmetayourself; the resolver is only used by the Agents SDK call path.