Skip to main content
Glama

Pausar perfil

wetaca_profiles_pause
Destructive

Stops tuppers from being sent to a Wetaca delivery profile by id or name. Runs as a dry-run by default; set confirm to true to apply the pause.

Instructions

Equivale a wetaca profiles pause <id|nombre>. Deja de enviar tuppers a ese perfil. Acepta el id o el nombre. 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": {
      "profile_ref": "<profile_ref>"
    },
    "name": "wetaca_profiles_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.
profile_refYesId o nombre del perfil, como en wetaca_profiles_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context on top: that nothing happens unless confirm:true is set, because the default is a dry run, and that confirm triggers --yes. It stops short of saying whether a paused profile can be resumed or what happens to already-scheduled deliveries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with zero filler, led by the CLI equivalence and the effect, then the accepted identifier form, then the dry-run default and confirm override. Everything an agent needs is front-loaded.

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, non-idempotent mutation with no output schema and fully documented params, the definition covers the dry-run safety default and the confirm escape hatch. The remaining gap is scope of the pause itself — whether it is temporary and reversible via the resume sibling — which an agent would have to infer.

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%, and the schema already documents profile_ref as id-or-name, confirm as the --yes switch, profile as the CLI session profile and debug as HTTP logging. The description only restates the id/name acceptance and the dry-run default, adding little beyond the structured fields, so baseline 3 applies.

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: pauses a profile, so tuppers stop being sent to it, and it accepts an id or name. That clearly separates it from resume-style siblings, but it never names wetaca_profiles_resume or the subscription/suggestion pause tools, so sibling differentiation is left implicit.

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 useful operational guidance — the call is dry-run by default and confirm:true maps to --yes — which implies a preview-then-confirm workflow. It does not say when to prefer this profile-level pause over wetaca_subscription_pause or wetaca_suggestion_pause, nor state any preconditions.

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