Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Image analyze

image_analyze
Read-onlyIdempotent

Analyze any public image URL (max 8 MB) with technical metadata plus Llama 3.2 11B Vision scene, object, and visible-text analysis. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL of a PNG/JPEG/WebP/GIF image
promptNooptional analysis prompt (3-500 chars)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

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?

The description adds real behavior beyond the annotations: an 8 MB size cap, a $0.005 per-call charge, the accepted payment rails, and the mandatory two-call x402 handshake. However, it leaves a notable tension: the annotations declare readOnlyHint=true while every call spends USDC/XNT, and the description never reconciles that or says what happens if payment verification fails or the URL exceeds 8 MB.

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?

Three sentences, front-loaded with capability, then cost, then the payment procedure, so the agent reads the critical facts first. The currency-and-chain roll-call ('USDC on Arc, Base or Solana, or XNT on X1') is dense but justified because an agent must know which rails are accepted.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe return values, which it does by enumerating metadata plus scene/object/text analysis. The paid-call mechanics and size limit are covered. Failure modes, latency expectations, and any distinction from the OCR sibling are the remaining gaps.

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 coverage is 100%, so all three parameters are already documented in the schema, and that sets the baseline. The description adds only the 8 MB ceiling (an indirect constraint on `url`) and a restatement of the `payment` handshake that the schema description already conveys.

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 and resource ('Analyze any public image URL') and enumerates what the analysis covers: technical metadata plus Llama 3.2 11B Vision scene, object, and visible-text analysis. It is clear what the tool does, though it never distinguishes itself from the sibling image_ocr despite overlapping on 'visible-text analysis'.

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

Usage Guidelines4/5

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

The payment workflow is spelled out precisely: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is clear invocation context an agent could otherwise get wrong. What's missing is when-to-use guidance against alternatives such as image_ocr or image_generate.

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.