Skip to main content
Glama

Pausar suscripción

wetaca_subscription_pause
Destructive

Pause a Wetaca subscription for a set number of weeks or indefinitely; set confirm:true to apply, or omit it to preview a summary without changing the account.

Instructions

Equivale a wetaca subscription pause. Pausa la suscripción. Con weeks (entero ≥ 1) es una pausa de N semanas; sin weeks es indefinida y se reactiva con wetaca_subscription_resume. 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.

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

Input Schema

NameRequiredDescriptionDefault
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
weeksNoSemanas de pausa. Si se omite, la pausa es indefinida.
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 que el CLI envía con la pausa (--feedback).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further by disclosing that there is no --dry-run, that an unconfirmed call exits with code 2 (confirmation_required) and applies nothing, and that confirm:true maps to --yes. That is exactly the kind of side-effect chain an agent needs before mutating a live subscription.

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 purpose, then progressively finer detail on weeks, dry-run absence, confirmation and feedback, with no filler. The terse CLI-flag shorthand ("No tiene --dry-run", "confirm:true envía --yes") is efficient but slightly telegraphic for readers unfamiliar with the wetaca CLI.

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 no output schema, the definition covers the key unknowns: reversibility path, confirmation semantics, and absence of a preview mode. It does not say what the applied response looks like or how an active pause affects pending deliveries, though these are secondary to calling 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 weeks, confirm, feedback, profile and debug are all already documented in the schema, and the description mostly restates them. Its real added value, the confirmation flow, is behavioral rather than per-parameter. Baseline 3 is appropriate.

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 ("Pausa la suscripción") and names the sibling that undoes it (wetaca_subscription_resume), so the agent can distinguish it from resume without opening a schema. The mapping to the underlying CLI command makes the scope unambiguous.

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?

Explicitly gives the two usage modes: with weeks it is an N-week pause, without weeks it is indefinite and undone via wetaca_subscription_resume. It also states the confirm precondition and that a call without confirm only prepares a summary. It does not contrast pausing against cancelling or other sibling alternatives, which keeps it short of a 5.

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