Retrieve a specific chunk from the RAG index by its chunk ID to fetch exact D&D 5e source content on demand.
Get a specific chunk from the RAG index by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| chunk_id | Yes | The chunk ID to retrieve (required) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It does not state whether retrieval is read-only-safe, what happens if the ID is not found, whether results are cached, or anything about error behavior. A single clear verb is not enough behavioral disclosure for a zero-annotation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the verb and resource. Nothing superfluous.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-param retrieval tool this covers the minimum, but with no annotations, no output schema, and multiple RAG siblings, the definition should clarify when to pick it over rag_search/batch_get and what it returns or errors on.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the one parameter is documented in the schema. The description merely restates 'by ID' without adding format, length, or source-context details beyond the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('a specific chunk from the RAG index') with scope indicator 'by ID'. Clear but does not distinguish itself from siblings like rag_search or batch_get beyond the singular-by-ID framing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by 'by ID' retrieval, but no explicit guidance on when to use this vs rag_search (search by content) or batch_get (multiple chunks). An agent can infer, but nothing routes it decisively.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.