Description

Context:

Currently, the FastMCP decorator path does not allow for any detailed parameter descriptions. It generates a basic schema of the input params based on the function signature. This means param description is missing.

However, with low-level.Server implementation, there's an inputSchema that clearly lets you define a description field for each param in a tool. Not to be confused with tool description itself.

Issue:

This led me down a wild goose chase and I learned that the Tool model itself is different between the two types of servers. The fastMCP Tool is defined in mcp.server.fastmcp.tools.base VS The low-level.Server Tool is defined in mcp.types.

I believe the FastMCP code was supposed to just abstract some of the server boilerplate, much like FastAPI. However, it seems like there's starting to be some significant divergence and feature disparity between the two types of servers.

tl;dr: Can we add descriptions for tool parameters, please?

References

Building off of - #323