Skip to main content
Glama

Canjear tarjeta regalo

wetaca_giftcards_redeem
Destructive

Redeem a Wetaca gift card code to add its balance to your wallet; the operation defaults to dry-run and executes only with confirm:true.

Instructions

Equivale a wetaca giftcards redeem <CODE>. Ingresa el saldo de una tarjeta regalo en el monedero. No es un pago con tarjeta bancaria. Por defecto --dry-run. confirm:true envía --yes.

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_giftcards_redeem"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCódigo de la tarjeta regalo.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the operation is dry-run by default and that confirm:true maps to --yes, i.e. the tool is inert unless explicitly confirmed. That is the key safety behavior for a destructive, non-idempotent tool. It still does not say what happens on an already-redeemed or invalid code.

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?

Four short sentences, front-loaded with the core action and immediately followed by the risk-relevant default. The CLI equivalence line is somewhat redundant but cheap and useful for mapping to the underlying command.

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

Completeness3/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 description covers the safety-critical confirm/dry-run behavior but says nothing about the result (wallet balance after redemption) or error conditions. Adequate but with clear gaps.

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 the baseline is 3; the description restates the confirm/--yes and dry-run mapping already documented in the schema property descriptions. It adds little semantic meaning beyond that.

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: it loads a gift-card balance into the wallet ('Ingresa el saldo de una tarjeta regalo en el monedero'). The line 'No es un pago con tarjeta bancaria' rules out a plausible confusion, but no sibling such as wetaca_vouchers_apply is named, so the differentiation is only partial.

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?

Usage context is implied (apply a gift card to the wallet), and the dry-run default is stated, but there is no explicit when-to-use vs. when-not guidance or pointer to any alternative tool. The 'only if the person asked for exactly this operation' condition lives in the schema, not in the description.

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