Skip to main content
Glama

SolSignal Web Tools

Image OCR

image_ocr
Read-only

OCR: extract text from an image URL (PNG/JPEG/GIF/TIFF/WebP). Languages: eng, deu, fra, spa, ita, por (join with +).

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": {
      "url": "<url>"
    },
    "name": "image_ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
langNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-fetch profile is covered. The description usefully adds supported formats and the language-code convention, but says nothing about size limits, failure behavior when no text is found, or what the response contains.

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?

Two short sentences, front-loaded with the action and followed by the format/language constraints. No filler or redundancy.

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?

For a two-parameter tool with one required input this is nearly sufficient, but with no output schema the description should indicate what comes back (raw text, structure) and how empty results are handled. Those gaps leave an agent guessing at the response shape.

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 only 50%: the url param has a description but lang is expressed purely as a regex. The description compensates well by listing the six valid language codes and the '+' joining syntax, adding real meaning beyond the pattern. It omits the URL length and public-http requirements, which the schema covers only partially.

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 an image URL') and enumerates supported image formats, so the tool's function is unambiguous. It does not explicitly differentiate itself from the sibling pdf_to_text, but the 'image URL' framing makes the input distinction implicit.

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 by the accepted input type (an image URL); there is no explicit when-to-use or when-not guidance, and no mention of routing to pdf_to_text for documents. An agent can infer the case, but nothing is 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.

Resources