Skip to main content
Glama

ocr_batch_vision

Extract text from multiple images in one batch and return consolidated OCR results using Apple Vision.

Instructions

OCR multiple images at once. Returns consolidated results.

Backend: vision. Apple Vision OCR — fast on-device GPU/ANE inference (macOS 10.15+). Best for CJK + major European languages. Zero install on macOS.

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_vision"
  }
}

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, the description carries the full burden; it does disclose the backend, platform requirement, and performance characteristics. It leaves out the mutation-free/read nature, how partial failures across a batch are handled, and what "consolidated results" actually contains.

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?

Two compact blocks with the core action front-loaded and backend facts grouped after. No filler, though the backend paragraph is dense with prose that could be tighter.

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?

For a batch tool with no output schema, no annotations, and zero schema coverage on three parameters, the description is thin: return shape, error behavior per image, and `mode`/`lang` semantics are all absent.

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% for all three parameters, and the description mentions none of them by name. The language note loosely gestures at `lang`, but the values it accepts and the `mode` parameter (default "accurate") are entirely undocumented 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?

"OCR multiple images at once" gives a specific verb (OCR) plus the batch scope, and "Backend: vision" implicitly separates it from the paddle/xiaomi batch siblings. It never names a sibling explicitly, so the differentiation relies on the reader decoding the backend suffix.

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?

It states the platform prerequisite (macOS 10.15+), the cost profile (zero install, on-device GPU/ANE), and the language sweet spot (CJK + major European languages), which is real selection guidance against the other backends. It stops short of explicit when-not-to-use or naming ocr_batch_paddle / ocr_batch_xiaomi as alternatives.

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