Skip to main content
Glama

Image To Text

image_to_text

Extract text from image using OCR (Optical Character Recognition).

Reads text from images like documents, screenshots, signs, etc.


Available models:

  • LightOnOcr_3_4B_Q8: input size=128-4096x127-4096

  • Nanonets_Ocr_S_F16: input size=128-4096x127-4096

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": {
      "image": "<image>",
      "model": "<model>"
    },
    "name": "image_to_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage file (base64 encoded or URL)
modelYesOCR model (e.g., 'Nanonets_Ocr_S_F16')
formatNoOutput format: 'text' or 'json'text
languageNoLanguage code for OCR (e.g., 'en', 'es', 'fr') - optional
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
return_result_in_responseNoReturn the extracted text inline in 'result'. Set to False to get only a download URL

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the two available OCR models and their input size ranges (128-4096 x 127-4096), but says nothing about job execution model, latency, cost, or failure behavior for oversized images.

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?

Front-loaded with the core action, followed by a short usage note and a compact model table. Every line is relevant, though the model list could be tightened into a single line.

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?

An output schema exists so return values need not be described, and all seven parameters are documented in the schema. Still, for a 7-parameter tool with webhook and async-style options, the description omits any mention of job behavior or how the webhook parameters interact with the inline result.

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 100%, so the baseline is 3, but the description adds real value by enumerating the concrete model identifiers and their resolution constraints, which the schema only gestures at with a single example. It does not, however, explain the format, language, or webhook parameters.

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 text from image using OCR') and clarifies the input domain (documents, screenshots, signs). It is clearly distinguishable from the pricing sibling image_to_text_price, though it never explicitly names alternatives.

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 second sentence implies when the tool applies by listing example image types, but there is no explicit when-not guidance, no mention of the price/estimate sibling, and no note on prerequisites such as supported formats or size limits beyond the model table.

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.