Skip to main content
Glama

Borrar dirección

wetaca_addresses_remove
Destructive

Deletes an unused Wetaca address by ID after a dry-run preview. Refuses to remove the subscription or current-week address until another one is assigned.

Instructions

Equivale a wetaca addresses remove <id>. Borra una dirección que no esté en uso. Si es la de la suscripción o la de la semana, el CLI se niega: primero hay que asignar otra con wetaca_addresses_save. 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": {
      "address_id": "<address_id>"
    },
    "name": "wetaca_addresses_remove"
  }
}

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.
address_idYesId numérico de la dirección (wetaca addresses list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds value beyond them by disclosing that the default is --dry-run and that confirm:true sends --yes. It also warns about the server-side refusal for in-use addresses, which the annotations cannot convey.

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 action, then the refusal case, then the safety default. The CLI-equivalence line is mildly redundant but helps map behavior to the underlying command.

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 one-required-param tool with full annotation coverage and a fully described schema, the definition supplies the missing pieces an agent needs: dry-run default, how to actually execute, and the precondition for a successful delete. Return values are not described, but no output schema exists and the CLI-equivalence hint covers it adequately.

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 schema already documents address_id, confirm, profile and debug. The description only reinforces the confirm/dry-run semantics that the schema already states, adding no new syntax or format detail beyond that baseline.

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 ("Borra una dirección") plus the CLI equivalent it wraps, which makes it immediately distinguishable from wetaca_addresses_save and wetaca_addresses_list. It also scopes the operation to addresses not currently in use.

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?

Gives an explicit blocking condition (if it is the subscription or week address the CLI refuses) and names the correct alternative, wetaca_addresses_save, to run first. It lacks a general when-to-use line versus list/save, but the constraint guidance is concrete and actionable.

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