Skip to main content
Glama

ocr_layout_paddle

Extract text with layout analysis using PaddleOCR, returning text blocks and bounding boxes from images. Supports language selection for document parsing and structured OCR workflows.

Instructions

Extract text with layout analysis. Returns blocks with bounding boxes.

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": {
      "path": "<path>"
    },
    "name": "ocr_layout_paddle"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • removedInput schema / properties / mode
      Removed value: -{
      -  "default": "base",
      -  "title": "Mode",
      -  "type": "string"
      -}
  2. First observedv1.0.0

TDQS

B3.4/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, and it does disclose a meaningful external dependency ('Requires PaddleOCR Python package') and a speed tradeoff. It does not say what happens if the package is missing, what input file types/URLs are accepted for 'path', or whether processing is local-only, which are the behaviors an agent most needs before invoking.

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 and return shape are front-loaded, then backend notes follow, with no wasted filler. The 'Backend: paddle' line mildly restates the tool name's suffix but still earns its place by anchoring the comparison to Vision.

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?

For a simple two-parameter OCR tool with no output schema, the description covers what it does and roughly what it returns (blocks with bounding boxes). It is not complete: parameter meaning, error behavior on missing dependencies, and the choice against the Xiaomi layout sibling 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 two parameters, so the description must compensate and largely does not: 'path' is never clarified as local file vs URL vs directory, and 'lang' is only obliquely gestured at via 'wider language support' with no code format or default behavior given.

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 ('Extract text with layout analysis') plus the return shape ('blocks with bounding boxes'), and the 'Backend: paddle' line lets an agent place it among the vision/xiaomi siblings. It stops short of naming a sibling explicitly, so differentiation relies on the reader mapping 'paddle' to the *_paddle naming family.

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 gives a real selection criterion against the Vision alternative: wider language support but slower performance. What's missing is any guidance versus ocr_layout_xiaomi or a statement of when this backend should be avoided entirely (e.g., no PaddleOCR installed).

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