Skip to main content
Glama

Cancelar pedido

wetaca_orders_cancel
Destructive

Cancel a confirmed Wetaca order and return the amount. Runs as a dry-run by default; set confirm to true to actually cancel. The order id comes from next deliveries or order history.

Instructions

Equivale a wetaca orders cancel <id>. Cancela un pedido confirmado y devuelve el importe. El id sale de wetaca_deliveries_next (pendientes) o wetaca_orders_list (historial). Por defecto --dry-run, sin efectos. confirm:true envía --yes y cancela de verdad. No toca tarjetas ni pagos pendientes.

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": {
      "order_id": "<order_id>"
    },
    "name": "wetaca_orders_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
confirmNoPor defecto false: no hay efectos en la cuenta. true equivale a --yes y ejecuta la operación. Úsalo solo si la persona pidió exactamente esta operación y ya vio el resumen.
profileNoPerfil de sesión de wetaca-cli (--profile). Si se omite, usa el perfil por defecto.
order_idYesId numérico del pedido a cancelar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the operationally decisive fact that the call is dry-run by default and only mutates when confirm:true is set, plus that a refund is issued. It does not cover re-invocation behavior on an already-cancelled order or what the response contains, which are the remaining behavioral gaps for a destructive tool.

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?

Five short sentences, front-loaded with purpose, then id provenance, then the dry-run/confirm distinction and the scope boundary. The leading CLI-equivalence line is somewhat redundant but still cheap and useful for CLI-mapped agents; nothing else is wasted.

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?

For a destructive, single-required-parameter tool with no output schema and full schema documentation, the description covers effect (refund), default safety (dry-run), the execution switch, and the boundary of what it touches. Missing only error/already-cancelled behavior, which is a modest gap rather than a blocking one.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more by explaining where order_id is obtained and by reinforcing that confirm:true is the real-execution switch rather than a routine flag. It does not elaborate on profile or debug, which is acceptable since the schema documents both.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource (cancel a confirmed order) and adds the outcome (the amount is refunded), which no sibling does. It also anchors itself with the CLI equivalent `wetaca orders cancel <id>` and names the two tools that supply the id, so an agent can place it in the workflow without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Guidance on when to use is concrete: the id comes from wetaca_deliveries_next for pending items or wetaca_orders_list for history, and the tool only applies to confirmed orders. A boundary is drawn ("No toca tarjetas ni pagos pendientes"), but there is no explicit statement of when not to cancel or what happens on a non-confirmed/already-cancelled order.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.