Skip to main content
Glama

No usar cupón

wetaca_vouchers_skip
Destructive

Skips a Wetaca voucher and pauses next week's delivery; runs as a dry run by default, requiring confirm:true to apply the change.

Instructions

Equivale a wetaca vouchers skip. AVISO del propio CLI: la API lo implementa como skipVoucher=true y TAMBIÉN pausa la entrega de la próxima semana, el mismo efecto que wetaca_suggestion_pause. Se deshace con wetaca_suggestion_resume. Por defecto --dry-run. confirm:true envía --yes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wetaca_vouchers_skip"
  }
}

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.
suggestionNoId de la sugerencia (--suggestion). Si falta, la próxima semana.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

It surfaces behavior annotations cannot express: the API implements this as skipVoucher=true but ALSO pauses next week's delivery, an undocumented side effect matching wetaca_suggestion_pause. It names the undo path and the default no-effect dry-run. This is exactly the extra context a destructive, non-idempotent mutation needs.

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?

Compact and front-loaded: equivalence first, then the warning, then undo and dry-run behavior. The opening equivalence restates the tool name somewhat, but every other clause carries real information. No padding.

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

Completeness5/5

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

For a destructive mutation with no output schema, the definition covers the surprising side effect, the reversal tool, and the safe-by-default execution model. An agent has everything needed to decide and to call it correctly.

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 all four parameters are already documented, including confirm and its --yes equivalence. The description reinforces the confirm/dry-run semantics but adds no new parameter meaning beyond the schema. Baseline 3 applies.

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 the operation by equivalence ("Equivale a `wetaca vouchers skip`") plus the title "No usar cupón", which together make clear it skips/declines the coupon. It also names the sibling whose effect it duplicates (wetaca_suggestion_pause), so an agent can separate it from neighbours. It falls short of a direct verb+resource sentence in prose, relying on the CLI equivalence.

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?

It gives concrete operating guidance: dry-run by default, confirm:true sends --yes, and the action is undone with wetaca_suggestion_resume. The explicit note that the effect equals wetaca_suggestion_pause is a useful routing signal. It stops short of an explicit 'use this instead of X when…' rule.

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