Skip to main content
Glama

Summarize an image and answer a question about it

describe_image
Read-only

Describes an image from an https URL or base64 (JPEG, PNG, GIF or WEBP, up to 4 MB): a short description, visible objects, whether it contains text, and the answer to an optional question. Uses Llama 3.2 11B Vision; the model's answers can be wrong. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlNohttps:// image address
imageNoOr base64 image data
questionNoOptional question about the image

Output Schema

NameRequiredDescriptionDefault
mimeNo
modelNo
answerNo
sourceNo
objectsNo
checkedAtNo
descriptionNo
containsTextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the underlying model (Llama 3.2 11B Vision), warns that answers can be wrong, states the exact price ($0.003 per successful call), the payment rail (x402, USDC on Base/Solana/10 more networks), and that failed calls are not charged. Cost, payment mechanics and accuracy caveats are precisely the behavioral context annotations cannot express.

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 states what is produced before any caveats, then a second sentence carries model, accuracy and pricing facts; no sentence is redundant. Dense but well-structured clause packing, with the size/format constraints placed next to the input description.

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?

Input constraints, expected outputs, model identity, accuracy caveat and billing model are all covered, and an output schema exists so return structure need not be spelled out. Nothing an agent needs in order to send a valid call or anticipate cost is missing.

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 description coverage is 100%, so the baseline is 3; the description adds real meaning by confirming the URL must be https, giving the base64 alternative and enumerating supported image formats with a 4 MB size limit. The only gap is that mutual exclusivity of url vs image is only implied by the word 'Or' rather than stated as a rule.

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 uses a specific verb and resource — 'Describes an image from an https URL or base64' — and enumerates the outputs (short description, objects, text presence, optional question answer), so an agent knows exactly what it gets back. It does not explicitly contrast itself with the near-named sibling 'image', which keeps it short of a 5.

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: the accepted input forms (https URL or base64), accepted formats (JPEG, PNG, GIF, WEBP) and 4 MB cap tell the agent when the tool is applicable, and the optional question implies a Q&A use case. There is no explicit when-to-use/when-not guidance nor a pointer to an alternative tool for other image operations.

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