Skip to main content
Glama

Reanudar perfil

wetaca_profiles_resume
Idempotent

Reactivate a paused Wetaca profile by ID or name. Runs as a dry-run by default; set confirm to true to apply the change to the account.

Instructions

Equivale a wetaca profiles resume <id|nombre>. Vuelve a activar un perfil pausado. 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_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.
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?

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, but give no hint that the tool is non-mutating by default. The description adds exactly that: 'Por defecto --dry-run' and that confirm:true sends --yes, which materially changes how risky the agent treats a readOnlyHint=false call. It stops short of describing what resuming does to the profile's session or whether a paused profile must exist.

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?

Three short sentences: identity/equivalence, effect, and the safety gate. The dry-run default is front-loaded before the confirm opt-in, which is the right order for a mutating operation. Nothing is redundant.

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 4-parameter, single-required-parameter tool with no output schema and full schema coverage, the description supplies the essential behavioral gate (dry-run vs --yes) and the target reference. It lacks only failure-mode detail, e.g. what happens if the profile is not paused, which the annotations do not cover either.

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's '--yes' semantics, which the description merely restates. `profile_ref` is tied to the same reference used in `wetaca_profiles_list`, a mildly useful cross-reference, but no new syntax or format detail is added. 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 — 'Vuelve a activar un perfil pausado' — and pins it to the CLI equivalent `wetaca profiles resume <id|nombre>`. It's clearly the inverse of the pause sibling, but it never names that sibling or any other resume-family tool, so differentiation is implied rather than explicit.

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 tells the agent the invocation is a dry-run by default and that confirm:true actually executes, which is real usage context. It gives no guidance on when to choose this over `wetaca_subscription_resume`, `wetaca_suggestion_resume`, or `wetaca_profiles_pause` (the inverse operation), and no prerequisites such as auth state are mentioned.

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