Skip to main content
Glama

recognize_table

Recognize a table from an image and return LaTeX tabular code. Provide image_url OR image_base64. model: deepseek-ocr (default), paddleocr-vl, or texify. Returns {latex, model, elapsed_ms}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recognize_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNodeepseek-ocr
image_urlNo
image_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the return shape ({latex, model, elapsed_ms}) and the available models. However, it is silent on what happens if both image inputs are supplied (precedence or error), on image size/format limits, and on failure behavior, which are meaningful gaps for an OCR call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose and output first, then the input constraint, then model options and return fields. Every clause carries information the schema does not, and nothing is padded.

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

Completeness4/5

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

For a simple three-parameter OCR tool with no annotations and no output schema, the description covers purpose, input mode, model choice, and return shape. The remaining omissions (input precedence, format/size limits, error behavior) are minor but real.

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

Parameters4/5

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

Schema description coverage is 0%, yet the description names all three parameters and enumerates the model values (deepseek-ocr default, paddleocr-vl, texify), information the schema lacks since it declares no enum. It does not explain accepted image formats or base64 encoding expectations, so it is strong but not exhaustive.

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 first sentence gives a specific verb (Recognize), a specific resource (table), an input type (image) and an output format (LaTeX tabular code). That alone distinguishes it from recognize_formula, but the description never explicitly names or contrasts the sibling, so it stops short of a 5.

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 only guidance is an input rule: 'Provide image_url OR image_base64.' There is no statement of when to choose this tool versus recognize_formula or list_ocr_models, and no prerequisites are given. Usage is inferable from the tool's purpose but never spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.