Skip to main content
Glama

Cerrar sesión

wetaca_auth_logout
DestructiveIdempotent

Clears the saved Wetaca authentication token from the local profile to log out. Requires confirm=true before running; re-login needs wetaca auth login in the terminal.

Instructions

Equivale a wetaca auth logout. Borra el token guardado en el perfil local. El CLI no pregunta; este servidor no llama al CLI hasta que confirm sea true. Para volver a entrar hace falta wetaca auth login en la terminal.

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

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.9/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: what exactly is destroyed (the locally stored token), that the CLI will not prompt for confirmation, and that the server defers the CLI invocation until `confirm` is true. It also discloses the recovery path (re-authentication requires `wetaca auth login` in a terminal), which no annotation conveys.

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 operation and its effect, then the confirmation gate and the recovery note. The opening 'Equivale a `wetaca auth logout`' is slightly redundant with the tool name, but it usefully signals CLI parity.

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-but-local action with no output schema and full parameter documentation, the description covers effect, confirmation gating, and how to recover. It does not say what happens when no token exists, but no essential information needed to call it correctly is missing.

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 description coverage is 100%, so `confirm`, `profile` and `debug` are already fully documented, making 3 the baseline. The description corroborates the gating semantics of `confirm` (no CLI call until it is true) but adds no format or default details the schema lacks.

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: it deletes the token saved in the local profile, and names the equivalent CLI command (`wetaca auth logout`). It is clearly distinguishable from `wetaca_auth_status` and from mutation siblings such as `wetaca_orders_cancel`, though it never explicitly contrast itself with those siblings.

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 only implied by the effect (log out / remove local credentials). The mention of `wetaca auth login` in the terminal is a recovery note rather than guidance on when to choose this over alternatives such as switching profiles via `wetaca_profiles_list` or checking state with `wetaca_auth_status`. No explicit when-not conditions appear in the description.

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