Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Describe image, ask about it: ask what is in an image or photo at a URL and get a text description or answer

describe
Read-only

Vision model for an image at a public URL: get a detailed description including any visible text, or pass a question to ask something specific about the image. Accepts PNG, JPEG, WebP and GIF up to 3 MB; a web page URL is read through its preview image (og:image). Use for alt text, OCR-style reading of screenshots, chart reading and content checks. Price $0.01/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of a PNG, JPEG, WebP or GIF image (max 3 MB), or of a web page whose preview image should be described
questionNoOptional question about the image (max 300 characters); default is a detailed description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: price ($0.01/call via x402 USDC or card key), failed calls free, and that repeat calls are charged — which explains the idempotentHint=false in practical terms. It also discloses format and 3 MB size limits and the og:image fallback for web page URLs, and confirms it computes only and changes nothing.

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?

Four dense sentences, front-loaded with capability, then constraints, then use cases, then cost and safety. Every sentence carries information an agent needs and there is no filler.

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?

No output schema exists, yet the description explains what comes back (a detailed description or an answer) and covers cost, input formats, size cap, and the URL-preview edge case. Nothing material for correct invocation is missing.

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% and both parameters are already documented in the schema, including the web-page preview behavior and the 300-character question limit. The description mostly restates the schema, so baseline 3 applies with only marginal added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Vision model for an image at a public URL' that returns a description or answers a question. The dual mode (describe by default vs. answer a question) is spelled out, which separates it from generation siblings like image_generate or pure text models.

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?

Gives concrete use cases: alt text, OCR-style screenshot reading, chart reading and content checks. It does not explicitly name a sibling to use instead or state when-not to use it, but the intended contexts are clear enough for an agent to route correctly.

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.