Skip to main content
Glama

Aplicar cupón

wetaca_vouchers_apply
Destructive

Applies a coupon code to next week's Wetaca delivery. Runs as a dry run by default; set confirm to true to execute the application.

Instructions

Equivale a wetaca vouchers apply <CODE>. Aplica un cupón a la entrega de la próxima semana. Por defecto --dry-run. confirm:true envía --yes. No canjea tarjetas regalo: para eso está wetaca_giftcards_redeem.

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": {
      "code": "<code>"
    },
    "name": "wetaca_vouchers_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCódigo del cupón.
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
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: the operation defaults to a dry run with no account effects unless confirm is set. It does not say whether an applied coupon replaces an existing one or how failures surface, which keeps it below a 5.

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?

Short and front-loaded: purpose first, then the safety default, then the sibling exclusion. The CLI equivalence line is useful only to CLI-literate agents but is compact and not wasteful.

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, non-idempotent mutation with no output schema, the description covers the safe-preview default, the execution switch, and the boundary against gift cards. Remaining gaps (replacement of existing discounts, error behavior) are modest.

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 five parameters are already documented in the schema, including confirm's --yes equivalence and suggestion's 'next week' default. The description restates the confirm/dry-run semantics rather than adding format or edge-case detail, so baseline 3 applies.

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 specific verb and resource ('Aplica un cupón a la entrega de la próxima semana') and explicitly excludes gift cards, naming the sibling that handles them. An agent can distinguish this from wetaca_giftcards_redeem without opening either 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?

Explains the safe default (dry-run) and what flips it to a real execution (confirm:true → --yes), plus the alternative for gift cards. It does not cover when to prefer vouchers_current or vouchers_list first, so it is clear context rather than full when/when-not guidance.

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