Skip to main content
Glama
Sign In
CHECK-MODULE MCP Server

CHECK-MODULE MCP Server

by muhammedehab35
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get-doc

Retrieve full documentation by ID. Access complete content from internal and official sources.

Instructions

Get full documentation by ID. Returns the complete content of a specific document.

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": {
      "id": "<id>"
    },
    "name": "get-doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states it returns complete content, which implies a read operation, but doesn't disclose any potential side effects, authentication needs, or rate limits. Adequate for a simple read.

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?

Two sentences, 14 words, front-loaded with action. Every word earns its place. No redundancy.

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

Completeness4/5

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

Given a single simple parameter and no output schema, the description is fairly complete. It tells what it does and what parameter is needed. Could mention error handling or return format, but adequate for a simple get-by-ID.

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% with one parameter 'id'. The description adds no additional meaning beyond the schema, which already documents 'Document ID'. Baseline score of 3 is appropriate.

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 'get full documentation by ID' with a specific verb and resource. It distinguishes from siblings like search-docs and list-categories, but could be more explicit about what constitutes 'full documentation'.

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

Usage Guidelines3/5

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

The description implies usage when you have a document ID, but provides no guidance on when to use this tool vs alternatives like search-docs or fetch-library-docs. No explicit when-not or exclusions.

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