Skip to main content
Glama

extract_pdf_result

Fetch the result of an extract_pdf job by task_id. Returns {task_id, status, content, chars}: content is the extracted text once status='done'; while still 'running' content is null — call again shortly. Results expire server-side, so fetch reasonably soon.

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": {
      "task_id": "<task_id>"
    },
    "name": "extract_pdf_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/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 load and delivers: it discloses the exact return shape ({task_id, status, content, chars}), the status-dependent nullability of content, the polling expectation, and the server-side expiry risk. Only permissions and rate-limit behavior remain undisclosed, which is minor for a read-by-id fetch.

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 tight clauses, front-loaded with purpose before return-shape detail, then the polling and expiry caveats. No filler sentences and nothing repeated from 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?

For a one-parameter async-result fetch with no output schema and no annotations, the description covers what it returns, how to interpret status, and the expiry constraint that would otherwise cause silent failures. Nothing an agent needs to call it 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?

One required parameter at 0% schema description coverage, so the description must compensate, and it does by naming task_id and framing it as the job handle from an extract_pdf call. That is the only semantic detail needed for a single-key lookup, though it stops short of format details like a prefix or ID length.

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?

States a specific verb ('Fetch') and resource ('the result of an extract_pdf job') plus the lookup key, and the reference to extract_pdf implicitly distinguishes it from the sibling that launches the job. An agent can immediately tell this is the retrieval half of an async pair.

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?

Explicitly instructs polling ('while still 'running' ... call again shortly') and warns to fetch soon before server-side expiry, which is real when-to-call guidance. It does not state the prerequisite that task_id must come from a prior extract_pdf call, so the context is clear but not fully spelled out.

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.