Skip to main content
Glama

Typebar (formerly SuperDocs)

get_attachment_status

Returns each attachment's processing state (pending/processing/completed/failed) plus extracted text length and chunk count once ready. Poll this after upload_attachment_base64 to know when an attachment becomes queryable by the AI. Surfaces processing errors with actionable messages.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_attachment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the returned state enum, the readiness signals (text length, chunk count), and that failures are surfaced with actionable messages. Gaps remain on polling cadence/backoff, whether the call is scoped to all attachments in the session or one, and behavior for an invalid session id.

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?

Three sentences, front-loaded with what is returned, then the usage trigger, then error behavior. No padding or restatement of the tool name; every sentence adds information.

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?

With no output schema and no annotations, the description does the heavy lifting by describing the return payload and error surfacing, which is enough for an agent to call it correctly. Only the polling lifecycle (cadence, termination) and the meaning of session_id are left implicit.

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 0%, so the single session_id parameter is documented nowhere. The description implies session-level scoping by saying "each attachment's" state, but it never states that session_id identifies the session whose attachments are listed, nor whether an attachment id can be supplied.

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?

A specific verb (returns) on a specific resource (attachment processing state) with the possible states enumerated inline (pending/processing/completed/failed) and the accompanying payload (text length, chunk count). An agent can immediately distinguish this from siblings like get_document_detail or list_session_documents.

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 names the exact trigger and the sibling that precedes it: "Poll this after upload_attachment_base64 to know when an attachment becomes queryable by the AI." That is a clear when-to-use rule tied to a named alternative. It stops short of saying when to stop polling or what to do if an attachment never leaves 'pending'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.