Skip to main content
Glama
mcp-library-docs

mcp-library-docs

by roznet

get_design_doc

Fetch the full content of a specific design document to get implementation details for functionality discovered via list_libraries.

Instructions

Returns the full content of a specific design document. Call this when you need implementation details for functionality discovered via list_libraries.

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": "<library>",
      "topic": "<topic>"
    },
    "name": "get_design_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic/document name without .md extension
libraryYesLibrary name as shown in list_libraries response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 the full behavioral burden. It implies a read-only retrieval and warns implicitly that the return is the 'full content' (potentially large), but says nothing about size limits, pagination, or behavior when a document or library is not found.

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, both front-loaded and purposeful: one states the action and return, the other states the trigger. There is no filler or redundancy.

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?

With no output schema and no annotations, the description is the only place to learn what comes back, and 'full content' does not specify format (e.g., raw markdown) or shape. For a two-parameter getter it is adequate, but it leaves the return value and failure modes underspecified.

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 both parameters (topic, library) are already documented in the schema, including the '.md' extension exclusion and the reference to list_libraries. The description adds no meaning beyond that, which is the baseline for full coverage.

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 uses a specific verb and resource ('Returns the full content of a specific design document'), which is unambiguous and clearly distinct from list_libraries (enumeration) and get_index_status (status check). It does not explicitly contrast itself with the siblings, but the retrieval-vs-listing distinction is evident.

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?

It gives an explicit trigger ('Call this when you need implementation details') and ties it to the preceding workflow step ('functionality discovered via list_libraries'), which tells the agent the prerequisite ordering. There is no explicit when-not guidance, but the selection context is clear.

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