Skip to main content
Glama

Image To Text Price

image_to_text_price

Calculates the price for OCR text extraction from an image, using the image itself or its width and height.

Instructions

Calculate price for OCR text extraction.

Pass the image, or its width and height.

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 observedv0.6.3

TDQS

B3.4/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 behavioral burden, and it does signal that this is a pure quote operation with no side effects. It does not say whether the call is free, whether the price is binding, or how the quote is scoped to a model. Output schema exists, so return values need not be explained.

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 short sentences, front-loaded with the purpose before the input note, with no filler. The second sentence largely paraphrases the schema, which keeps it from a 5.

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?

A simple quoting tool with a full schema coverage and an output schema, so expectations are modest. Still, the required model parameter and the notion that this returns a quote without performing extraction are left implicit, leaving an agent to infer the core contract.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents image, width, height, model, and language, making 3 the baseline. "Pass the image, or its width and height" usefully reinforces the either/or input path, but adds no syntax, format, or constraint detail 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?

States a specific verb and resource: "Calculate price for OCR text extraction." The word "price" clearly differentiates it from the sibling image_to_text, which performs the extraction itself, so an agent can distinguish quote from execution. It does not, however, name any sibling explicitly.

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 is only implied: a pricing tool is presumably called before running OCR, but the description never says when to use this versus image_to_text, nor that the call is a free quote that performs no extraction. The one piece of guidance given is input-shape advice (image, or width and height).

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