Skip to main content
Glama
Sign In
MCP-researcher Server

MCP-researcher Server

by clssck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_documentation

Retrieve documentation and usage examples for technologies, libraries, or APIs to understand implementation details and best practices.

Instructions

Get documentation and usage examples for a specific technology, library, or API

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": {
      "query": "<query>"
    },
    "name": "get_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe technology, library, or API to get documentation for
contextNoAdditional context or specific aspects to focus on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the primary function and reveals nothing about potential side effects, output format, source reliability, or limitations. The agent is left guessing about what 'documentation' entails (e.g., official docs, community examples, version specifics).

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 a single, concise sentence that front-loads the main verb and resource. There is no wasted wording or unnecessary detail.

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 simple tool with full schema coverage and no output schema, the description is minimally viable but lacks usage guidance and behavioral context. It could be more complete by explaining what types of documentation are returned or how it differs from sibling tools.

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 coverage is 100% for both parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides; it merely reiterates 'specific technology, library, or API' which matches the 'query' parameter description.

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 clearly states the verb ('Get') and the resource ('documentation and usage examples') for a 'specific technology, library, or API.' This is specific and distinguishes it from generic search, though it doesn't explicitly call out sibling tools.

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?

No guidance is given on when to use this tool versus alternatives like search, find_apis, or chat_perplexity. The description implies a documentation-focused purpose but provides no exclusions, prerequisites, or contextual cues for selection.

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

Deploy Server

Other Tools