Skip to main content
Glama

img_tools_rotate

[$x402 pago por llamada] Rota una imagen en múltiplos de 90°. 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": {
      "degrees": "<degrees>",
      "file_base64": "<file_base64>"
    },
    "name": "img_tools_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
degreesYesDebe ser 90, 180 o 270.
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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that output is always PNG and that each call is paid via x402 (with the 402-response behavior detailed in the schema), but it omits limits, error behavior, and what happens if a non-multiple-of-90 value is passed.

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 short sentences with the payment tag front-loaded and the operation stated immediately. Slightly terse but nothing wasted; the bracketed payment marker is mildly cryptic but efficient.

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?

With no output schema, the description correctly fills the gap by declaring the return format (PNG), and the payment requirement is disclosed. For a simple single-operation image utility with fully documented parameters, this is close to sufficient, missing only error/size constraints.

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%, so the schema already documents degrees, file_base64, and x_payment thoroughly. The description adds the PNG-output fact but no additional parameter semantics beyond what the schema states, making baseline 3 appropriate.

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 ('Rota una imagen') plus the exact constraint (múltiplos de 90°) and the output format (siempre PNG). This distinguishes it from img_tools_resize and img_tools_crop, though it never names those siblings explicitly.

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?

The 'múltiplos de 90°' phrasing implies when the tool applies (orthogonal rotations), but there is no explicit when-to-use/when-not guidance and no mention of when img_tools_convert or img_tools_resize would be preferable.

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