Problem
When debugging MCP tools in MCP Inspector the UI does not expose field descriptions from the schema.
Why this matters
The inputSchema is the main contract an MCP client or agent uses to understand how to call a tool correctly.
Field descriptions are especially important because they explain the intent of each argument.
https://modelcontextprotocol.io/specification/draft/server/tools#protocol-messages
Evn
MCP Inspector v0.21.2
UPD:
I see, it’s already used as a placeholder for each input.
That’s why it was hidden when the fields had default values.
It’s probably reasonable to display it below the input so it remains visible even when we have default values.
New issue is makes sence.
related issue #1388 about format/validation
Problem
When debugging MCP tools in MCP Inspector the UI does not expose field
descriptionsfrom the schema.Why this matters
The
inputSchemais the main contract an MCP client or agent uses to understand how to call a tool correctly.Field descriptions are especially important because they explain the intent of each argument.
https://modelcontextprotocol.io/specification/draft/server/tools#protocol-messages
Evn
MCP Inspector v0.21.2
UPD:
I see, it’s already used as a placeholder for each input.
That’s why it was hidden when the fields had default values.
It’s probably reasonable to display it below the input so it remains visible even when we have default values.
New issue is makes sence.
related issue #1388 about format/validation