Skip to main content
Glama

get

Fetches a single chunk's full text and location using a chunk_id from a prior result, enabling follow-up reading of relevant content.

Instructions

Fetch a single chunk's full text + location by chunk_id (from a prior result).

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

Input Schema

NameRequiredDescriptionDefault
chunk_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the operation returns full text plus location and that the chunk_id should come from a prior result, but it does not describe behavior for invalid or missing chunk_ids, permissions, or any limits.

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 efficient sentence with the key operation and lookup source front-loaded. Every element earns its place.

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?

This is a simple one-parameter read tool with an output schema, so return-value details need not be repeated. The description covers the essential input provenance and output content, with only minor gaps around error behavior.

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?

Schema description coverage is 0%, so the description must add meaning to the single parameter. It does so by explaining that chunk_id comes from a prior result, which gives the agent clear provenance for the value; it still does not clarify integer format or error handling.

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 names a specific verb ("Fetch") and resource ("a single chunk's full text + location") and identifies the lookup key (chunk_id). It clarifies scope versus broader search/query siblings by specifying a single chunk from a prior result, though it does not explicitly name an alternative tool.

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 phrase "from a prior result" implies this tool is used to expand a specific chunk already seen in an earlier query or recall response. However, it does not state when not to use it or compare it explicitly against sibling tools such as query or recall.

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