Skip to main content
Glama

Context7

by io.github.upstash

Query Documentation

query-docs
Read-onlyIdempotent

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.

You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Do not call this tool more than 3 times per question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to look up in the library's documentation, scoped to a single concept. Be specific and include relevant details, but keep each query to one topic — if the user's question spans multiple distinct concepts, make a separate call per concept instead of combining them, unless the question is about how the concepts interact. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad (too vague): 'auth' or 'hooks'. Bad (too broad): 'routing and auth and caching in Next.js'. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
libraryIdYesExact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful behavioral context beyond those annotations: results are 'up-to-date,' the prerequisite ID-resolution step is mandatory, calls are limited to 3 per question, and sensitive data must not be included in queries. Minor gaps like error handling or response shape are not disclosed, but the added operational context is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, stating the core purpose in the first sentence. The following sentences add only high-value operational instructions: ID resolution prerequisite, the exception for user-provided IDs, and the call limit. There is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low parameter count, rich schema descriptions, and strong safety annotations, the description provides everything an agent needs to invoke the tool correctly: purpose, prerequisite flow, ID format source, call limit, and query hygiene guidance. No critical missing context is apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters have rich descriptions with examples, formatting guidance, and scoping rules. The tool description itself does not add much parameter-level detail beyond what the schema already provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Retrieves and queries') on a specific resource ('up-to-date documentation and code examples from Context7') and clarifies it applies to 'any programming library or framework.' This distinguishes it clearly from the sibling tool resolve-library-id, which resolves IDs rather than querying documentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: call 'Resolve Context7 Library ID' first unless the user supplies a library ID in a recognized format. It also provides a hard usage constraint ('Do not call this tool more than 3 times per question'), leaving no ambiguity about the intended call flow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Context7 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one resolves library names to IDs, the other queries documentation. There is no overlap; they operate in a sequential dependency, but each has a unique role.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in kebab-case: 'resolve-library-id' and 'query-docs'. The naming is uniform and predictable, making it easy for agents to understand their function.

Tool Count3/5

With only 2 tools, the server feels extremely minimal, which is borderline for a documentation query service. While the two tools cover the core workflow, the count is on the low end, making it feel slightly thin for a general-purpose documentation tool.

Completeness4/5

The workflow is complete for the stated purpose: resolve a library ID, then query docs. There are no obvious gaps in the lifecycle, though the server lacks features like listing all available libraries or direct version-specific queries without resolution, which are minor omissions.

Resources