Skip to main content
Glama

Image To Text Price

image_to_text_price

Calculate price for OCR text extraction.

Pass the image, or its width and height.


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

Input Schema

NameRequiredDescriptionDefault
imageNoImage to quote (URL, data URI or base64); its size is read from it
modelYesOCR model name
widthNoImage width in pixels (required if image not provided)
heightNoImage height in pixels (required if image not provided)
languageNoLanguage code (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden, and it does add real behavioral context by listing the supported models and their per-model input size bounds (128-4096 x 127-4096). Those bounds are stricter than the schema's 1-10240 width/height limits, so the information is genuinely new. It does not address cost units, whether the quote reserves capacity, or what happens on oversized input, which keeps it from 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?

The purpose and the image-or-dimensions rule are front-loaded in the first two lines, with model details following as reference material. The structure is scannable and free of filler. The horizontal rule adds a little visual noise but no meaning.

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

Completeness5/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 no explanation, and all five parameters are documented in the schema. What remains is the model enumeration and its size constraints, which the description supplies. For a pricing calculator this is enough for an agent to call it correctly.

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; the description raises that by enumerating the two legal values for `model`, a free-form string with no enum in the schema. The per-model size limits also explain how the `width`/`height` parameters are actually validated. It says nothing about the optional `language` parameter or the accepted URL/data-URI/base64 forms beyond what the schema states.

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 opens with a specific verb and resource: "Calculate price for OCR text extraction." That clearly separates quoting from performing OCR, which is the distinction an agent needs against siblings such as image_to_text. It never names an alternative tool, so the differentiation is inferred from the verb 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?

It gives a usable input rule - supply the image, or supply width and height - which tells the agent how to call it in two different situations. It gives no guidance on when to use this quote versus actually running image_to_text, and no mention of prerequisites such as authentication or credits.

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.