Skip to main content
Glama
zackscriven

lemma_docs_mcp

by zackscriven

Get Lemma Docs Chunks

lemma_docs_get
Read-onlyIdempotent

Fetch full text of Lemma documentation chunks by ID or by document path, expanding excerpts from search results. Use after discovery to read complete sections.

Instructions

Fetch the full text of specific indexed Lemma documentation chunks by id, or every chunk of one document by its relative path. Use this after lemma_docs_context to expand excerpts you actually need — do not use it to browse (use lemma_docs_context for discovery). Reads the local corpus index only; it NEVER calls live Lemma or banking APIs.

Args:

  • ids (string[], 1-8, optional): Chunk ids exactly as returned by lemma_docs_context.

  • path (string, optional): A relative corpus path exactly as returned in a result's 'path' field; returns all chunks of that document in order.

  • response_format ('markdown' | 'json', default 'markdown'): Text rendering; structured content is always attached. At least one of ids or path is required.

Returns (structured): { found: [{ id, namespace, source_type, path, heading, text, metadata }], missing: [string], truncated?, truncation_message? }

Examples:

  • ids=["lemma-docs-docs-guides-deposit-bonuses.md#md-1-0"] -> full text of that section.

  • path="lemma-docs-docs-guides-mso-pc-compliance.md" -> every chunk of that document (may truncate; follow the truncation message).

Errors:

  • Calling with neither ids nor path returns an error explaining both options.

  • Unknown ids/paths are reported in 'missing' rather than failing the whole call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoChunk ids exactly as returned by lemma_docs_context (e.g. "lemma-docs-docs-guides-deposit-bonuses.md#md-1-0"), up to 8 per call.
pathNoA relative corpus path exactly as returned in a previous result's 'path' field. Returns every chunk of that document, in order.
response_formatNoText output format: 'markdown' for human-readable (default) or 'json' for the full machine-readable object.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
missingYes
truncatedNo
truncation_messageNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial behavioral context beyond that: it 'NEVER calls live Lemma or banking APIs,' unknown ids/paths are reported in 'missing' rather than failing the call, and truncation is possible with a message to follow. This is exactly the kind of non-obvious behavior an agent needs to know.

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 front-loaded with purpose and usage, then organized into Args, Returns, Examples, and Errors sections. Every section earns its place, and the content is dense but non-redundant with the schema.

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

Completeness5/5

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

The description covers validation behavior, missing-id behavior, truncation, live-API boundaries, return shape, and examples for both access modes. Given the output schema exists and the annotations cover safety, nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

The input schema already documents all three parameters with clear descriptions, so the baseline is 3. The description adds meaningful extras: the critical 'at least one of ids or path is required' constraint that is absent from the schema, the difference in what each mode returns, and concrete examples. This goes beyond the schema without having to carry the full parameter-documentation burden.

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 opens with a specific verb-resource pair: 'Fetch the full text of specific indexed Lemma documentation chunks by id, or every chunk of one document by its relative path.' It clearly distinguishes the tool from its sibling lemma_docs_context by framing this tool as the expansion step, not the discovery step.

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

Usage Guidelines5/5

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

The description explicitly says to use this tool after lemma_docs_context to expand excerpts and warns 'do not use it to browse (use lemma_docs_context for discovery).' This is direct, unambiguous routing guidance that names the alternative tool and the condition that selects it.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zackscriven/lemma-docs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server