Skip to main content
Glama

Make a PDF searchable with OCR

ocr_pdf
Idempotent

Recognise the text in your scanned PDFs so you can search, select and copy it, without changing how they look. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per page.

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": {
      "files": "<files>"
    },
    "name": "ocr_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With annotations already covering the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description goes further by disclosing that the original's appearance is unchanged, that the result is delivered as a download link retained only about an hour, and that paid plans cost 5 credits per page. The main undisclosed trait is processing latency or whether a status poll is ever needed.

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 short sentences: what it does and the benefit first, then the return/delivery detail, then the cost. Every sentence contributes information an agent or user would actually need.

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?

For a one-parameter tool with no output schema, the description covers the outcome, the return mechanism with its expiry, and billing impact, which is nearly everything needed. Only the execution model (sync vs. async, expected duration) is missing.

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 100% for the single 'files' parameter, including URL vs. base64 object forms and the 20 MB cap, so the schema carries the semantics. The description adds no file-format or input-shape detail beyond it, making the baseline 3 appropriate.

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 and resource ('Recognise the text in your scanned PDFs') and immediately names the user-visible outcome (search, select, copy), which cleanly separates it from transform siblings like pdf_to_word or compress_pdf. Nothing about the operation is left ambiguous.

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 'your scanned PDFs' implies the right input condition, but there is no explicit when-to-use or when-not guidance, no mention of what happens with already-text-layer PDFs, and no pointer to job_status if processing is asynchronous. Usage is inferable rather than stated.

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.

Resources