Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

ai_ocr

[$0.02] Extract structured text lines, confidence scores, and full-page transcripts from public HTTPS image URLs or base64 PNG/JPG documents using local EasyOCR.

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": "ai_ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlNoPublic HTTPS URL of PNG/JPG image
detail_levelNo'standard' or 'compact'standard
image_base64NoBase64-encoded PNG/JPG image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two valuable traits: a $0.02 cost and that processing is local via EasyOCR. It is silent on failure modes, size/format limits, whether both input fields are mutually exclusive, and turnaround behavior, so the safety and constraint picture remains incomplete.

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?

A single front-loaded sentence with the price first, then output, then accepted inputs, then engine. No filler and no 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?

With no output schema, the description helpfully enumerates what is returned (lines, confidence, transcripts), which covers the main gap. However, for a paid tool with three optional parameters it omits detail_level semantics and does not state which of image_url/image_base64 wins if both are supplied, leaving non-trivial ambiguity for invocation.

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 all three parameters and the baseline is 3. The description adds only that URL and base64 are alternative input modes ("or"), and never mentions detail_level or its 'standard'/'compact' values, so it adds little beyond the schema.

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 ("Extract") and precise outputs (text lines, confidence scores, full-page transcripts) over specific inputs (public HTTPS image URL or base64 PNG/JPG). An agent can distinguish this from audio-oriented siblings like ai_transcribe, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the many ai_* siblings. The only implicit guidance comes from the accepted input formats, which tells the agent what is valid but not when this tool is the right choice.

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