Skip to main content
Glama

ocr_batch_paddle

Extract text from multiple images at once using the PaddleOCR CPU backend and return consolidated results. Supports multi-language OCR when you need batch text extraction across files.

Instructions

OCR multiple images at once. Returns consolidated results.

Backend: paddle. PaddleOCR CPU — cross-platform, mature model. Wider language support than Vision, but slower. Requires PaddleOCR Python package.

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": {
      "paths": "<paths>"
    },
    "name": "ocr_batch_paddle"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
modeNoaccurate
pathsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / properties / mode / default
      Previous value: -"base"New value: +"accurate"
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does add real value by disclosing the runtime dependency ('Requires PaddleOCR Python package') and the CPU/cross-platform/slower performance profile, but it never covers failure behavior on unreadable files, output ordering, or whether the result set is per-image keyed to input paths.

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?

Front-loaded with the purpose and return behavior, then backend rationale, all in three short sentences. The 'Backend: paddle' line partially restates the tool name, but the surrounding model description earns its place by driving the sibling comparison.

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

Completeness2/5

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

There are no annotations, no output schema, and zero schema coverage on three parameters, so the description is the only source of truth — yet 'consolidated results' leaves the return shape undefined and the mode parameter is undocumented entirely. For a batch tool where per-file partial failure is the expected complication, that gap matters.

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%, so the description must compensate for all three parameters and does not. 'Images' loosely maps to paths, and 'wider language support' hints at lang without giving codes or defaults, while the mode parameter (default 'accurate') and its possible values are never mentioned anywhere.

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?

States a specific verb and resource ('OCR multiple images at once') plus a return characteristic ('consolidated results'), which distinguishes it from single-image siblings like ocr_text_paddle. The backend note ('paddle') and the comparison to Vision separate it from ocr_batch_vision, though the sibling is never named directly.

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?

Gives genuine selection context by contrasting with the Vision backend: better language coverage but slower, which is exactly the trade-off an agent needs when choosing among the batch tools. It stops short of explicit when-not guidance or naming the alternative tool, so it stops at 4.

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