Update MCP tool call customisation docs #2817
Conversation
MasterOdin
force-pushed
the
docs-tool-call-customisation
branch
from
9917ade to
e896eda
Compare
Signed-off-by: Matthew Peveler <[email protected]>
MasterOdin
force-pushed
the
docs-tool-call-customisation
branch
from
e896eda to
b8fb2a4
Compare
| @@ -169,7 +169,39 @@ The MCP servers provide the ability to set a `process_tool_call` which allows | |||
| the customisation of tool call requests and their responses. | |||
|
|
|||
| A common use case for this is to inject metadata to the requests which the server | |||
| call needs. | |||
| call needs. Accessing the metadata is then SDK specific, for example with the | |||
There was a problem hiding this comment.
Thanks for adding het new section, can you add it below the existing example though? I think the flow of "here's how to send metadata", "here's how to receive it" is more clear.
There was a problem hiding this comment.
To clarify, you're asking for the flow to be:
A common use case for this is to inject metadata to the requests which the server call needs.
mcp_process_tool_call.pycode example
mcp_server.pycode examplePlease note, how to access the metadata is SDK specific, for example with the MCP Python SDK, it is accessible via the Context parameter for tool calls as shown above.
There was a problem hiding this comment.
@MasterOdin I was thinking:
A common use case for this is to inject metadata to the requests which the server call needs:
mcp_process_tool_call.pycode exampleHow to access the metadata is MCP server SDK specific. For example with the MCP Python SDK, it is accessible via the Context parameter for tool calls:
mcp_server.pycode example
Closes #2616
Updates the MCP tool call customisation docs so that:
mcp_server.pyscript so that the entire thing is runnable as-is which demonstrates the behavior