Skip to main content
Glama

ocr_table_paddle

Extract tables from images and return structured CSV or JSON data via PaddleOCR for cross-platform table recognition.

Instructions

Extract tables from an image. Returns structured CSV/JSON.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • removedInput schema / properties / lang
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Lang"
      -}
    • removedInput schema / properties / mode
      Removed value: -{
      -  "default": "base",
      -  "title": "Mode",
      -  "type": "string"
      -}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the engine (PaddleOCR on CPU), platform coverage (cross-platform), relative performance (slower), and a hard dependency (PaddleOCR Python package must be installed). It does not cover failure modes or path handling, keeping it short of a 5.

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 tight, front-loaded segments: purpose and return type first, backend characteristics second. Nearly every clause carries information, though 'mature model' is mild filler and the backend note could be compressed into a single when-to-prefer sentence.

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 one-parameter extraction tool with no annotations and no output schema, the description adequately covers optimization choice and the return format. The notable gap is the required 'path' argument, which is undocumented in both schema and description, leaving an agent unsure what to pass.

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?

The single parameter 'path' has 0% schema description coverage, and the description says nothing about it — it does not clarify whether it is a local file path, a URL, or a directory. The description's only related hint is 'from an image', which is thin compensation for a fully undocumented required parameter.

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 ('Extract tables from an image') and adds a return format (CSV/JSON) plus a named backend ('paddle'). It implicitly contrasts with the Vision siblings ('Wider language support than Vision'), but never names ocr_table_vision or ocr_table_xiaomi explicitly, so differentiation is inferred rather than stated.

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 tradeoff note ('wider language support than Vision, but slower') gives an implicit selection criterion between backends, which is real guidance. However, there is no explicit when-to-use/when-not statement and no named alternative tool, so an agent must map 'Vision' to the sibling names itself.

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