Fix guides · check docs.params

Describe every tool parameter, with format and an example

Parameters without a description are the commonest cause of wrong arguments on the first call.

5,936 of 15,338 reachable MCP servers (38.7%) have this issue today.

Why it matters

Measured across 300k live tools, about one in six has undocumented parameters. The model sees only the name; "id" could be a numeric id, a slug or a URL.

Before

"properties": { "id": { "type": "string" } }

After

"properties": { "id": { "type": "string", "description": "Repository in owner/name form, e.g. modelcontextprotocol/servers" } }

TypeScript SDK

inputSchema: { id: z.string().describe("Repository in owner/name form, e.g. modelcontextprotocol/servers") }

Python SDK

def get_repo(id: Annotated[str, Field(description="Repository in owner/name form, e.g. modelcontextprotocol/servers")]): ...

Check your server

Paste your endpoint at /check, or run it in CI:

pipx run glimind check https://your-server.example.com/mcp --min-grade B

Related

• Give every tool parameter a type