Skip to main content
Glama

recognize_formula

Recognize a math formula from an image and return LaTeX. Provide image_url (downloaded server-side) 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_formula"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNodeepseek-ocr
image_urlNo
image_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it reveals that image_url is fetched server-side (a meaningful side effect an agent must know), that base64 is an alternative, the available model backends with their default, and the exact response shape. It omits any statement about failures, image size/format limits, or whether exactly one input must be provided.

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, each earning its place: purpose first, then input contract, then model choices, then return shape. No redundant restatement of the tool name or title.

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?

No output schema exists, but the description spells out the return object, which is exactly what is needed. For a three-parameter OCR tool with zero annotation coverage, the only real gap is undefined behavior when zero or two image inputs are given.

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 coverage is 0% and the schema has no enums, so the description does real work: it explains the download semantics of image_url, states the two image inputs are alternatives, and enumerates the three legal model values with the default. It does not clarify what happens if both image inputs are supplied or if neither is.

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 names a specific verb (Recognize), a specific resource (a math formula from an image) and the concrete output (LaTeX), which inherently separates it from a sibling like recognize_table. It stops short of explicitly naming the sibling it is not, so it does not reach the top tier.

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?

Usage guidance is only implied: an agent can infer this is the tool for formula images, and it is told to supply image_url OR image_base64. There is no explicit when-to-use/when-not-to-use statement and no reference to alternatives such as recognize_table or the local PDF extraction tools.

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.