Description is 2006 chars (maximum 1500) — move detail into parameter descriptions.
Very long tool descriptions are paid for in every conversation. Detail that only matters once a parameter is used belongs in that parameter's description.
Context7 MCP server tool surface audit
A99/100composite score
- Token footprint
- ~1,053
- Tools
- 2
- Findings
- 2
- Scanned
Context7's MCP server publishes 2 tools. Loaded into a conversation, those definitions occupy roughly 1,053 tokens of context before anyone types a word. MCP Surface Lint scores that surface 99 out of 100 (grade A), with 2 scored findings spread across 2 of the six rule categories.
Surface is the strongest category at 100/100, and descriptions the weakest at 97/100. It is catalogued here under Developer Tools, alongside other servers agents reach for in the same kind of work.
Token footprint
At 1,053 tokens the surface takes about 1% of a 200,000-token context window, and it takes it on every turn — this is rent, not a one-off cost. That averages 527 tokens per tool definition, counted with the o200k_base encoding.
Against a category median of 2,797 tokens, this surface runs about 62% below the middle of the pack.
surface100
naming100
descriptions97
schemas100
annotations100
design97
Findings
Every finding below names the rule behind it and the tool it fired on.
One finding comes from `descriptions/too-long`. Very long tool descriptions are paid for in every conversation. Detail that only matters once a parameter is used belongs in that parameter's description. On this surface it fires on `resolve-library-id`.
One finding comes from `design/list-no-limit`. A list/search tool with no limit or pagination parameter can dump an unbounded payload into the context window. The caller must be able to ask for less. On this surface it fires on `query-docs`.
warn 2 findings
Findings that measurably degrade tool selection.
"query-docs" implies list/search output but has no limit or pagination parameter — result size is unbounded.
A list/search tool with no limit or pagination parameter can dump an unbounded payload into the context window. The caller must be able to ask for less.
What this surface does well
Context7 scores a full 100 in surface, naming, schemas and annotations, which is to say the surface stays inside a sensible tool and token budget, the tool names follow one convention end to end, the input schemas are typed tightly enough to constrain what a model sends and read and write operations are machine-distinguishable before a client runs them.
Tool inventory
Cost is concentrated in `resolve-library-id`: 643 tokens, some 61% of everything Context7 ships, while `query-docs` costs 408. Every tool carries a description, ranging from 429 to 2,006 characters.
All 2 declare annotations, so a client can tell a read from a write before running one. Across the surface, schemas carry 2 top-level parameters on average and reach a maximum depth of 1.
All 2 tools as published, heaviest first. Token counts use the o200k_base encoding and are approximate.
| Tool | Tokens | Description | Params | Required | Depth | Annotations |
|---|---|---|---|---|---|---|
resolve-library-id | 643 | 2006 chars | 2 | 2 | 1 | yes |
query-docs | 408 | 429 chars | 2 | 2 | 1 | yes |
How this compares
Within Developer Tools this is rank 2 of 5 scanned servers — 3 points above the category median of 96.
The closest comparisons in this directory are DeepWiki, Filesystem and Playwright, which sit nearest on score and face the same kind of surface-design pressure.
- Category
- Developer Tools
- Rank in category
- 2
- Category median score
- 96
- Category median tokens
- 2,797
Want this surface fixed, not just measured?
Get a fix planA fix plan turns these findings into an ordered set of changes with the token saving of each one.
This page is a static analysis of Context7's published tools/list surface on the date shown. It is not a security review, a performance benchmark, or a judgement of the product behind the surface. Read how the score is computed, or browse every audited server.