Skip to main content
Glama

img_tools_metadata

[$x402 pago por llamada] Lee dimensiones, formato y campos EXIF de una imagen, sin modificarla.

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": {
      "file_base64": "<file_base64>"
    },
    "name": "img_tools_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
file_base64YesContenido del archivo codificado en base64 (o data URL). Se convierte a multipart/form-data internamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose two important traits: the call is paid ($x402 per call) and it does not mutate the image. It stops short of stating supported formats, size limits, or failure behavior beyond the 402 case documented in the schema.

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?

One tightly written sentence with the payment caveat front-loaded in brackets and the core read action immediately after. No waste, though the '$x402 pago por llamada' tag is terse enough to be slightly cryptic for an unfamiliar agent.

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 usefully names the return contents (dimensions, format, EXIF fields). Combined with the payment note and non-destructive guarantee, that covers what an agent needs to call it; only format/error detail 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 description coverage is 100% with only two parameters, and both are fully documented in the schema (base64/data URL input, optional X-PAYMENT header). The description adds nothing about parameter syntax or constraints, so the baseline 3 applies.

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 ('Lee dimensiones, formato y campos EXIF de una imagen') and adds scope ('sin modificarla'), which implicitly separates it from mutating siblings like img_tools_strip_exif or img_tools_convert. It never names an alternative explicitly, but the operation is unambiguous.

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: read this tool when you need image metadata without altering the file. There is no explicit when-to-use/when-not-to-use guidance or pointer to strip_exif/resize/convert as alternatives, leaving the routing inference to the agent.

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