Skip to main content
Glama

img_tools_resize

[$x402 pago por llamada] Redimensiona una imagen (filtro Lanczos3). Siempre devuelve PNG sin importar el formato de entrada.

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

Input Schema

NameRequiredDescriptionDefault
widthYes
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

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden and does contribute two real facts: the call is paid via x402 and the output is always PNG. It stays silent on failure modes, maximum dimensions, whether aspect ratio is preserved or the image is stretched, and what the 402 flow looks like beyond the bracketed tag.

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?

Two tight sentences with the core action front-loaded and no filler. The bracketed '[$x402 pago por llamada]' tag is terse to the point of being cryptic, but it is compact rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations means the description must cover behavior end to end, and for a 4-parameter mutation-of-bytes tool it omits input limits, aspect-ratio behavior, and error/402 handling. The two undocumented dimension parameters leave an agent guessing at the most important inputs.

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 50%: file_base64 and x_payment are documented in the schema, but width and height have no descriptions anywhere. The description does not compensate — it never says whether those are absolute pixels, target-bounding-box values, or whether aspect ratio is respected.

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 ('Redimensiona una imagen') plus the resampling algorithm (Lanczos3), and discloses the fixed output format (always PNG regardless of input). It does not explicitly distinguish itself from siblings like img_tools_convert, img_tools_crop or img_tools_rotate, which all touch the same resource.

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 pick this over img_tools_convert (which likely also changes format/size) or img_tools_crop. The only contextual signal is the payment note, which tells the agent a cost exists but not when the tool is the right choice.

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