Problem
When debugging MCP tools in MCP Inspector, the tool form renders fields from inputSchema, but the UI does not expose the data type and validation from the schema. This makes it hard to debug whether the MCP server is exposing a good schema for agents/clients.
Why this matters
The inputSchema is the main contract an MCP agent uses to understand how to call a tool correctly.
https://modelcontextprotocol.io/specification/draft/server/tools#protocol-messages
Evn
MCP Inspector v0.21.2
Problem
When debugging MCP tools in MCP Inspector, the tool form renders fields from inputSchema, but the UI does not expose the
data type and validationfrom the schema. This makes it hard to debug whether the MCP server is exposing a good schema for agents/clients.Why this matters
The
inputSchemais the main contract an MCP agent uses to understand how to call a tool correctly.https://modelcontextprotocol.io/specification/draft/server/tools#protocol-messages
Evn
MCP Inspector v0.21.2