Skip to main content
Glama

Saltar la semana

wetaca_suggestion_pause
Destructive

Skip the next week's Wetaca delivery tied to a suggestion while leaving the already charged week unchanged; set confirm to apply, or the CLI returns a summary and confirmation_required.

Instructions

Equivale a wetaca suggestion pause. Salta la entrega de la próxima semana. La semana ya cobrada no se toca. 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. Opcional: feedback y suggestion (id; si falta, el CLI usa la próxima).

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

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.
feedbackNoComentario opcional (--feedback).
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

A3.9/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses concrete behavior an agent could not otherwise know: there is no --dry-run, calling without confirm exits with code 2 (confirmation_required) and applies nothing, confirm:true forwards --yes, and an already-charged week is left untouched. These are exactly the operational details that prevent a destructive call from going wrong.

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?

The description is dense and front-loaded: identity of the tool, scope, the charged-week caveat, then the confirmation mechanics. It is telegraphic and mixes CLI switch names with account-level semantics, but each sentence carries operational information rather than filler.

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 mutation with full annotation and schema coverage and no output schema, the definition covers the confirmation gate, the no-dry-run constraint and the charged-week boundary. What is left implicit is whether a skip can later be undone (the existence of `wetaca_suggestion_resume` suggests it can, but the description does not say so).

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 every parameter is already documented in the schema, including confirm, feedback, suggestion and the default of using the next suggestion. The description only restates that feedback and suggestion are optional and that a missing suggestion id falls back to the next one, adding little beyond the structured field text.

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 names a specific verb and scope: it skips next week's delivery ('Salta la entrega de la próxima semana') and maps to the CLI command `wetaca suggestion pause`. An agent can tell what it does, but it does not distinguish itself from the similar-looking siblings `wetaca_subscription_pause` or `wetaca_profiles_pause`, leaving the agent to infer the difference from names alone.

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 is implied rather than stated: the tool is for skipping the upcoming week and nothing else. The description does explain the confirmation protocol (no confirm = summary + exit code 2, no change applied), which effectively signals the safe calling path, but it never says when to prefer this over the subscription/profile pause siblings or when skipping is inappropriate.

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