Skip to main content
Glama

Franjas de entrega

wetaca_deliveries_options
Read-onlyIdempotent

Lists available delivery time slots for the subscription postal code or a supplied zipcode and marks the current option. Read-only; returned IDs can be used to set a delivery slot.

Instructions

Equivale a wetaca deliveries options. Franjas horarias disponibles para el código postal de la suscripción, o para el zipcode que pases. Marca cuál es la actual. Solo lectura. El id se usa en wetaca_deliveries_set_option.

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

Input Schema

NameRequiredDescriptionDefault
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
profileNoPerfil de sesión de wetaca-cli (--profile). Si se omite, usa el perfil por defecto.
zipcodeNoCódigo postal (--zipcode). Si falta, el CLI usa el de la suscripción.

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Solo lectura' merely repeats them. The description does add behavior beyond the annotations: that the response flags the currently active slot and that the returned id is the input for wetaca_deliveries_set_option, which is the key downstream contract.

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 front-loaded sentences: identity, scope, current-marker, safety, and the id handoff. Minor waste in the alias line ('Equivale a `wetaca deliveries options`') and the redundant 'Solo lectura' given the annotations, but nothing obscures the core message.

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?

No output schema exists, and the description covers the essentials an agent needs: what the result contains (available slots), how to identify the active one, and how to reuse the id. It stops short of describing the slot fields themselves or ordering, but that gap is small for a read-only lookup.

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 all three parameters (debug, profile, zipcode) are already documented in the schema. The description restates the zipcode fallback to the subscription's postal code but adds no format or precedence detail beyond what the schema says, so the baseline 3 applies.

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+resource: available delivery time slots (franjas horarias) for either the subscription's postal code or a supplied zipcode, plus the fact that it marks the current one. It also names the sibling that consumes the returned id (wetaca_deliveries_set_option), so an agent can separate this read tool from the mutating one without opening either schema.

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?

Implicitly clear about when to use it: to discover which delivery windows exist and which one is currently selected, before calling wetaca_deliveries_set_option with the returned id. It lacks an explicit 'do not use this to change the option' exclusion, but the routing to set_option covers the main ambiguity.

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