Skip to main content
Glama
inboxd
by 47star

get_attachment_text

Reads extracted attachment text in bounded segments so AI agents can retrieve long attachments without loading entire files. Specify an offset and length to page through content.

Instructions

Read extracted attachment text in bounded segments.

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_attachment_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
lengthNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints at segmentation behavior, which is genuinely useful, but says nothing about what happens if no text has been extracted, whether the result is truncated, permission/auth requirements, or how the caller knows it received only a partial slice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler, and the key qualifier ('bounded segments') is placed where it is read immediately. It is efficient, though its brevity is partly the cause of the gaps above rather than pure economy.

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

Completeness2/5

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

A three-parameter read tool with no annotations and no output schema needs the description to explain paging semantics, extraction preconditions, and return shape. None of that is present, so an agent can guess the call but cannot confidently page through or interpret results.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters (id, length, offset) rest on bare field names. 'Bounded segments' gestures at length/offset paging but gives no units, no default-slice size, no note that length caps at 20000, and no explanation of how offset interacts with the extracted text. The description does not compensate for the documentation gap.

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 ('Read') and a specific resource ('extracted attachment text'), with the qualifier 'in bounded segments' that signals paginated content retrieval rather than metadata listing. That distinguishes it in spirit from get_attachments, but it never names the sibling or explicitly contrasts the two, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of preconditions (e.g. that the attachment's text must already be extracted/synced), and no named alternative for when a caller wants metadata instead of text. The phrase 'extracted attachment text' weakly implies the reader must fetch metadata first, but the agent is left to infer the workflow.

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