xpay✦ DevTools Collection

query-docs

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

You must call 'resolve-library-id' 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.

IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The question or task you need help with. Be specific and include relevant details. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad: 'auth' or 'hooks'. 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.
`libraryId`	Yes	Exact 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.

First observedMar 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the tool retrieves up-to-date docs and imposes a 3-call limit, but it does not describe the return format, error handling, or any side effects. This is partial transparency but not comprehensive, earning a middle score.

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 concise and front-loaded. The first sentence states the purpose, the second gives the crucial prerequisite, and the third sets a usage restriction. Every sentence earns its place, with no filler or redundant information.

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

Completeness3/5

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

For a tool with no output schema and no annotations, the description provides enough to begin using it but does not specify what the returned documentation looks like or how errors are communicated. The prerequisite and call limit are useful, but more detail about return values and failure modes would make it more complete.

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%, so the baseline is 3. The description reinforces the need to obtain libraryId from resolve-library-id, but this information is also present in the schema. The query parameter examples are helpful but already in the schema. No significant additional semantic value is provided.

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 clearly states the tool's function: retrieving and querying up-to-date documentation and code examples from Context7 for any library or framework. It uses specific verbs ('Retrieves and queries') and a specific resource ('documentation and code examples from Context7'), which distinguishes it from sibling tools like microsoft_docs_search or npmSearch.

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

Usage Guidelines4/5

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

The description provides explicit usage guidelines: it requires calling resolve-library-id first unless the user supplies an ID in a specific format, and it sets a hard limit of 3 calls per question with a fallback instruction. However, it does not mention alternative tools or when not to use this tool, so it misses the 'alternatives' part of the rubric.

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

All xpay✦ DevTools Collection tools Inspect

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

C2.4/5.0

Disambiguation2/5

Several tools have overlapping or ambiguous purposes that could confuse an agent. For example, analyze_code, analyze_patterns, and analyze_design_patterns all involve code analysis with unclear boundaries, while check_deceptive_patterns and check_placeholders seem like subsets of analyze_code. The NPM tools form a coherent group but are distinct from the rest, creating a fragmented toolset.

Naming Consistency2/5

Naming conventions are highly inconsistent across the toolset. Some tools use snake_case (e.g., analyze_code, execute_code), others use camelCase (e.g., npmAlternatives, npmChangelogAnalysis), and there are mixed styles like query-docs with hyphens. The NPM tools follow a consistent npmPrefix pattern internally, but this is not applied to other tools, leading to overall chaos.

Tool Count2/5

With 39 tools, this server is overloaded for a 'DevTools Collection' scope. The count feels excessive, as many tools could be consolidated (e.g., multiple analysis tools) or logically grouped. While the NPM tools are numerous but focused, the overall set lacks cohesion, making it cumbersome for an agent to navigate and select appropriate tools efficiently.

Completeness3/5

The toolset covers a broad range of development tasks, including code analysis, execution, documentation, and package management, but there are notable gaps. For example, there is no tool for code generation or refactoring, and the Microsoft and NPM tools are well-covered but isolated from other functionalities. The surface is extensive but not fully integrated, with some dead ends in workflow transitions.

Resources

Need Help?