Skip to main content
Glama

Reactivar la semana

wetaca_suggestion_resume
Idempotent

Reactivates a skipped delivery for next week and reverses the effect of wetaca_vouchers_skip. Returns a summary without applying changes unless confirm is true.

Instructions

Equivale a wetaca suggestion resume. Vuelve a activar la entrega de la próxima semana si estaba saltada. También deshace el efecto de wetaca_vouchers_skip. No tiene --dry-run. Sin confirm, el CLI prepara el resumen y sale con código 2 (confirmation_required) sin aplicar el cambio. 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_suggestion_resume"
  }
}

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.2/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that there is no --dry-run, that without confirm the CLI only prepares a summary and exits with code 2 (confirmation_required) without applying anything, and that confirm:true forwards --yes. That two-phase confirmation protocol is essential operational behavior the annotations (readOnlyHint=false, idempotentHint=true) do not convey.

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?

Front-loaded with the effect, then the relationship to vouchers_skip, then the confirmation mechanics — every sentence carries information. Slightly dense and the CLI-equivalence clause is mild boilerplate, but nothing 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 mutating, idempotent tool with no output schema, the description covers the confirmation gate, the exit-code behavior, and the relationship to the skip operation. It omits what happens when the week was not skipped and any auth/profile prerequisite, which are the remaining gaps.

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 schema already documents all four parameters; the baseline would be 3. The description nevertheless adds meaning about confirm's consequences (exit code 2 and no applied change unless true), which is more concrete than the schema's 'equivale a --yes' phrasing.

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 reactivates next week's delivery if it had been skipped, and explicitly notes it reverses the effect of wetaca_vouchers_skip. The inverse sibling (wetaca_suggestion_pause / skip) is only implied by the conditional phrasing rather than named, so it falls just short of the top mark.

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?

The condition for use is explicit ('si estaba saltada' — if it was skipped) and the related tool wetaca_vouchers_skip is named as the thing being undone. It does not state a when-not-to-use case or name the pause/skip sibling directly, so it is clear context without full exclusion guidance.

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