Skip to main content
Glama

Cambiar franja

wetaca_deliveries_set_option
Destructive

Changes the delivery time slot for a Wetaca subscription and next week's delivery using an option ID from available delivery options; runs as dry-run by default until confirmed.

Instructions

Equivale a wetaca deliveries set-option <id>. Cambia la franja de entrega de la suscripción y de la próxima semana. El id sale de wetaca_deliveries_options. 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": {
      "option_id": "<option_id>"
    },
    "name": "wetaca_deliveries_set_option"
  }
}

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.
option_idYesId numérico de la franja (wetaca deliveries options).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructive/non-idempotent/openWorld, but the description adds the crucial detail that the default is --dry-run with no account effects until confirm:true maps to --yes. It also discloses blast radius (current subscription plus next week's delivery). No auth or return-value info, but the dry-run default is the key behavioral fact and it is stated.

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 CLI equivalent and immediately followed by the effect and the id source. Tight and scannable; the CLI-equivalence opener is the only arguably non-essential line.

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 mutation with a 100%-documented schema and no output schema, the description covers what changes, the safe default, and how to commit. It stops short of stating reversibility or whether the previous slot can be restored, which would matter for a destructive op.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 all four parameters, but the description adds useful provenance for option_id by pointing at wetaca_deliveries_options. It also restates the dry-run/--yes mapping for confirm, mildly reinforcing rather than duplicating schema text.

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 ('Cambia la franja de entrega') and scopes it precisely: it changes the subscription's slot and next week's. It also names the sibling tool that supplies the id (wetaca_deliveries_options), so an agent can distinguish reading options from applying one.

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?

Makes the workflow precondition explicit — the id must come from wetaca_deliveries_options — and flags the default dry-run with confirm:true as the way to actually execute. It lacks explicit when-not-to-use guidance, but the read-vs-apply split against the options tool is clear.

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