Skip to main content
Glama

Guardar dirección de entrega

wetaca_addresses_save
Destructive

Saves a new delivery address and assigns it to the subscription and next week's delivery; defaults to dry-run and requires confirm to apply.

Instructions

Equivale a wetaca addresses save. Crea la dirección y la asigna a la suscripción y a la próxima semana (el mismo flujo que la web: saveAddress, editDeliveryAccountInfo, editSuggestionDelivery). Obligatorios: street, number, zipcode, city. Opcionales: floor, notes, firstname, lastname, phone; si faltan, el CLI hereda los de la dirección actual. Por defecto --dry-run. Cada ejecución real crea una dirección nueva: no es idempotente. 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": {
      "street": "<street>",
      "number": "<number>",
      "zipcode": "<zipcode>",
      "city": "<city>"
    },
    "name": "wetaca_addresses_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCiudad (--city).
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
floorNoPiso (--floor).
notesNoNotas para el repartidor (--notes).
phoneNoTeléfono (--phone). Si falta, se hereda.
numberYesNúmero (--number). El CLI lo trata como texto.
streetYesCalle (--street).
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.
zipcodeYesCódigo postal numérico (--zipcode).
lastnameNoApellidos (--lastname). Si falta, se hereda.
firstnameNoNombre (--firstname). Si falta, se hereda.

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?

Adds real context beyond the annotations: default dry-run, non-idempotency (every real run creates a new address), inheritance of optional fields from the current address, and confirm:true mapping to --yes. It is consistent with destructiveHint=true and idempotentHint=false, though it never says what happens to the previous address or whether the subscription's current delivery is overwritten.

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?

Three dense sentences that front-load the effect and then constraints; almost nothing is wasted. The internal flow names (saveAddress, editDeliveryAccountInfo, editSuggestionDelivery) are marginally useful for parity but border on noise for an agent choosing a tool.

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 12-parameter destructive write tool with no output schema, the definition covers side effects, the safety gate, idempotency and inheritance. What is missing is modest: validation/error behavior and exactly which existing state gets replaced when an address is reassigned.

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?

With 100% schema description coverage, the schema already explains every parameter including the confirm gate and the inheritance of phone/firstname/lastname. The description restates the required/optional split and inheritance but adds no format, constraint, or precedence detail beyond 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?

States a specific verb and resource (creates the delivery address) plus its side effects: assignment to the subscription and to next week's delivery, and names the web flow it mirrors. It is clear what the tool does, but it does not distinguish itself from siblings such as wetaca_suggestion_edit, which could plausibly also touch next week's delivery.

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?

Implied usage is clear (create/replace the delivery address for the subscription), and the --dry-run default plus confirm:true gate give operational guidance. However, there is no explicit when-to-use vs. when-not, and no sibling is named as an alternative for editing an existing address without creating a new one.

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