Skip to main content
Glama

img_tools_strip_exif

[$x402 pago por llamada] Elimina todo metadato EXIF/XMP re-codificando la imagen desde el buffer de píxeles decodificado.

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

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.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that all EXIF/XMP metadata is destroyed, that re-encoding occurs from pixel data, and that payment is required per call. It does not clarify output format, whether the original image format is preserved, or any rate-limit details.

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?

The description is a single front-loaded sentence with no wasted text. It conveys the payment context, the core action, and the technical mechanism efficiently.

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?

For a simple two-parameter image transformation with no output schema, the description covers purpose and key behavior but omits return-value details. An agent can infer it returns a stripped image, but the definition does not state the output format or whether the original is modified in place.

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 both parameters are already fully documented in the input schema. The description adds no parameter-specific details, which is acceptable when the schema does the heavy lifting, but it does not compensate with extra guidance.

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 states a specific verb and resource: it removes all EXIF/XMP metadata by re-encoding the image from the decoded pixel buffer. This clearly distinguishes it in practice from metadata-inspection tools, although it does not name any sibling tool 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?

Usage is only implied by the action itself: remove metadata when EXIF/XMP must be stripped. The description does not state when to choose this over img_tools_metadata or img_tools_convert, nor does it mention exclusions or prerequisites beyond the payment note.

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