Fix guides · check efficiency.heavy_tools

Trim oversized tool definitions

A few tools with very long descriptions or schemas often account for most of a server's token cost.

862 of 15,360 reachable MCP servers (5.6%) have this issue today.

Why it matters

Long examples, changelogs and full API docs inside a description are paid for on every request. Keep the description to when-to-use and what-it-returns; put the rest in a resource or the README.

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