Skip to main content
Glama

SizeMyFile

Make a PDF searchable

ocr
Idempotent

Recognize scanned text with OCR when needed. Scanned-page OCR uses the server. Existing PDF text is preserved. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the mutation/idempotent/non-destructive profile, and the description adds real context beyond that: OCR runs as a queued job returning a run ID for progress and output tracking, server-side processing is used for scanned pages, and the operation consumes cloud allowance (a quota/cost signal). It still doesn't say what happens to prior outputs or how long runs take, hence not a 5.

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?

Five short, front-loaded sentences with the core action and the key async/cost facts up front. It is efficient, though the telegraphic phrasing leaves several claims (e.g. 'uses the server', 'cloud allowance') unexplained rather than tightening them.

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

Completeness3/5

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

The async run/ID behavior and cost signal are covered, and an output schema exists so return values needn't be spelled out. However, for a 4-parameter tool with a nested options object and 0% schema coverage, the description leaves an agent guessing about the artifacts list, the required idempotency key, and how options interact with OCR.

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% across 4 parameters, including a nested options object with output format, byte bounds, resize/upscale and compression mode, plus allow_server_fallback. The description explains none of these; 'Uses cloud allowance' only faintly gestures at the server-fallback parameter.

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 states a specific verb and resource: recognize scanned text with OCR to make a PDF searchable. It is clear what the tool does, but it never names or differentiates itself from adjacent tools such as document_text or office_pdf, so sibling routing is left to inference.

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?

'Recognize scanned text with OCR when needed' plus 'Existing PDF text is preserved' implies the condition (pages without a text layer) and reassures on mixed documents, but there is no explicit when-not guidance and no named alternative for plain text extraction.

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.