Skip to main content
Glama

context7_docs

Read-onlyIdempotent

Retrieve library documentation with a read-only query using a fixed HTTPS endpoint and library ID, without sending project files.

Instructions

Opt-in read-only Context7 documentation lookup using a fixed HTTPS endpoint; never sends project files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "library_id": "<library_id>",
      "query": "<query>"
    },
    "name": "context7_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
library_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description still contributes real behavioral context: it uses a fixed HTTPS endpoint and never sends project files, which is meaningful for an open-world network call. It omits failure behavior, rate limits, and what a result looks like, so it adds some but not rich value.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the scope (opt-in, read-only) and the privacy guarantee are both stated compactly. Slightly more structure separating what it does from its safety properties would read better, but nothing is wasted.

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?

The tool is simple (two required string params, no output schema, rich annotations), so the description does not need to explain return values. However, for a lookup tool whose parameters have zero schema documentation, the omission of any parameter guidance and any selection criteria against sibling library tools leaves real gaps.

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

Parameters2/5

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

Schema description coverage is 0% and both required parameters are undocumented, so the description carries the full burden here. It adds nothing about library_id format (presumably a Context7-style library identifier) or what query should contain, leaving the agent to infer both from parameter names alone.

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

Purpose4/5

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

The description names a specific resource and action ('Context7 documentation lookup') plus its scope qualifiers ('opt-in', 'read-only'), so an agent knows it retrieves external library documentation rather than project files. It does not differentiate itself from sibling library tools such as design_library_guidance or design_library_catalog, leaving 'Context7' and 'opt-in' as the only distinguishing signals.

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

Usage Guidelines2/5

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

'Opt-in' implies the tool is not invoked by default but never states the condition under which an agent should choose it, nor what to do instead when it is not opted in. There is no explicit when-to-use, when-not-to-use, or named alternative.

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