Skip to main content
Glama

Listar direcciones

wetaca_addresses_list
Read-onlyIdempotent

Lists saved Wetaca delivery addresses for an account so you can review destinations before updating orders or delivery profiles. Read-only.

Instructions

Equivale a wetaca addresses list. Direcciones guardadas. Solo lectura.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 the phrase 'Solo lectura' merely restates structured data. The description adds nothing beyond that — no indication of ordering, pagination, or what a saved address entry contains, despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments with no filler, which is appropriately sized for a simple read tool. The first fragment ('Equivale a `wetaca addresses list`') is largely redundant for an agent that already has the tool name, so not every sentence fully earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with rich annotations and 100% schema coverage, the definition is minimally sufficient to call it correctly. It is thin on what the tool actually returns — no output schema exists and no description of the address record shape — but nothing critical for invocation 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%, and both parameters (debug, profile) are fully documented in the schema, so the description is not required to compensate. It contributes nothing about either parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition tells the agent this maps to `wetaca addresses list` and returns saved addresses, which is enough to distinguish it from the save/remove address siblings. However, it never states a verb or scope directly, relying on the CLI equivalence and the noun phrase 'Direcciones guardadas' to imply a listing operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as wetaca_addresses_save or wetaca_addresses_remove. The agent must infer that this is the read path of the addresses group from the name alone.

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