Skip to main content
Glama

img_tools_crop

[$x402 pago por llamada] Recorta un rectángulo de la imagen. Siempre devuelve PNG.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "file_base64": "<file_base64>"
    },
    "name": "img_tools_crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesEsquina superior izquierda del recorte.
yYes
widthYesDimensiones del recorte — `x+width` y `y+height` no pueden superar el tamaño de la imagen.
heightYes
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

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden but does disclose two meaningful traits: a per-call x402 payment model and a guaranteed PNG output format. It omits error behavior (out-of-bounds coordinates), rate limits, and whether the source image is preserved, so it is only partially transparent.

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?

Two compact sentences with the billing tag front-loaded and the output guarantee as a closing constraint. No wasted verbiage.

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 6-parameter tool with no annotations and no output schema, the description covers billing and return format but not the shape of the returned payload (base64? data URL?), maximum input size, or failure modes. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% — 'y' and 'height' lack descriptions, and 'x_payment'/'file_base64' are documented in-schema. The description adds nothing about parameters (no coordinate origin, units, or size limits beyond what the schema already says), so it does not compensate for the gap.

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 ('Recorta un rectángulo de la imagen') plus a definite output guarantee ('Siempre devuelve PNG'), which separates it from img_tools_resize/rotate/convert. It does not name a sibling or state when cropping applies, 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 Guidelines2/5

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

No guidance on when to crop versus resize, rotate, or convert, and no mention of prerequisites beyond the payment tag. The agent must infer the use case entirely from the verb.

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