OCR Beans

ocr_page

Extract text from specific pages of a PDF, useful for large files or follow-up OCR when you only need selected pages.

Instructions

Extrai texto de páginas específicas de um PDF.

Útil para PDFs grandes onde você só precisa de algumas páginas,
ou para follow-up após usar ocr_pdf em um documento grande.

Args:
    pdf_path: Caminho absoluto do arquivo PDF.
    pages: Páginas a extrair. Formatos aceitos: "1", "1-5", "1,3,7", "2-4,8".
    dpi: Resolução para OCR (150, 200, 300 ou 400). Default: 300.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dpi`	No
`pages`	Yes
`pdf_path`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 16, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses useful operational detail (accepted page-range syntax, DPI choices and default) but says nothing about permissions, local file requirements, cost/time of OCR, or read-only nature, leaving real behavioral gaps.

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?

Purpose is front-loaded in the first sentence, followed by a usage sentence and a clean Args block. Every element is informative, though the structure is conventional rather than tight.

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?

An output schema exists, so return values need not be explained. For a three-parameter OCR tool, the description covers purpose, usage context, and all parameter syntax adequately; nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: it defines pdf_path as an absolute path, enumerates accepted page formats with four concrete examples, and lists the valid DPI values plus the default. This is richer than the bare schema types.

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 (extract text from specific PDF pages) and immediately scopes it against the whole-document sibling by framing it as page-selective. An agent can tell this apart from ocr_pdf and batch_ocr without opening a schema.

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 gives two use cases: large PDFs where only a few pages are needed, and follow-up after running ocr_pdf on a large document. It names the alternative it complements, though it never states when *not* to use it (e.g., for whole documents, prefer ocr_pdf).

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

Deploy Server