Skip to main content
Glama

Reanudar suscripción

wetaca_subscription_resume
Idempotent

Reactivate a paused Wetaca subscription and return alreadyActive if it is running; requires confirm:true to apply changes, otherwise it returns a summary.

Instructions

Equivale a wetaca subscription resume. Reactiva una suscripción pausada. Si ya está activa, el CLI responde alreadyActive sin volver a activarla. 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_subscription_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=false and idempotentHint=true, and the description reinforces the idempotency by explaining that an active subscription returns alreadyActive without re-activation. It adds behavior the annotations cannot express: there is no --dry-run, and without confirm the CLI exits with code 2 (confirmation_required) without applying the change. It omits any cost or billing consequence of reactivation, which would have earned 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?

Four short sentences, front-loaded with the outcome and followed by the edge case and the confirmation flow. The opening equivalence clause restates the tool identifier but does useful work by mapping to the CLI verb.

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?

Three optional parameters, no output schema, and annotations already covering safety; the description supplies the outcome states (applied, alreadyActive, confirmation_required) that an agent needs in order to interpret the result. It is close to complete, with only the absence of cost or side-effect disclosure keeping it at 4.

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 parameters are already well documented, and the description mostly reinforces the confirm semantics already stated in the schema. The added value is the exit-code-2 behavior before confirmation, which exceeds what the schema says; debug and profile are left to the schema.

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?

"Reactiva una suscripción pausada" states a specific verb and resource, and the CLI equivalence anchors it precisely. It implicitly separates it from the pause sibling by naming the paused→active direction, but never names the inverse tool explicitly.

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?

It gives real when-conditions: it only does something if the subscription is paused, and it reports alreadyActive otherwise. However, it never routes the agent to the alternative operation (pause) or states the precondition that the subscription must currently be paused; the guidance is implied rather than spelled out.

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