Description
Summary
It would be great if the SDK supported passing a meta field when defining tools, allowing developers to include additional metadata directly in the tool decorator.
Motivation
Currently, the SDK does not support passing a meta field during tool definition, limiting flexibility for attaching structured metadata such as descriptions, categories, or configuration details.
For example
frommcp.serverimportfastmcpmcp=fastmcp.FastMCP(...)
@mcp.tool(meta={...})defmy_tool():
...Comparison
In the latest version of the FastMCP package, this functionality is already supported:
fromfastmcpimportFastMCPmcp=FastMCP(...)
@mcp.tool(meta={...})defmy_tool():
...Expected behavior
The server SDK should support the meta argument when defining tools, consistent with the FastMCP implementation.
References
No response
Description
Summary
It would be great if the SDK supported passing a meta field when defining tools, allowing developers to include additional metadata directly in the tool decorator.
Motivation
Currently, the SDK does not support passing a meta field during tool definition, limiting flexibility for attaching structured metadata such as descriptions, categories, or configuration details.
For example
Comparison
In the latest version of the FastMCP package, this functionality is already supported:
Expected behavior
The server SDK should support the meta argument when defining tools, consistent with the FastMCP implementation.
References
No response