Skip to main content
Glama

Historial de pedidos

wetaca_orders_list
Read-onlyIdempotent

List previous Wetaca orders with pagination to review order history; supports limit, offset, and optional session profile.

Instructions

Equivale a wetaca orders list. Pedidos anteriores. limit por defecto 10 en el CLI; offset por defecto 0. 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_orders_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
limitNoMáximo de pedidos (--limit). El CLI usa 10 si falta.
offsetNoDesplazamiento (--offset). El CLI usa 0 si falta.
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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's "Solo lectura" merely restates that. It adds the CLI defaults for limit and offset, but those are already documented in the schema, so no genuinely new behavioral context (ordering, page bounds, response shape) is supplied beyond structured fields.

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 very short sentences with no filler. It is front-loaded with the CLI equivalence rather than the purpose, and the telegraphic fragments take slightly more effort to parse than one clear sentence would, but nothing is wasted.

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 simple read-only list tool with full schema coverage and rich annotations, the essentials are covered, but the description omits the ordering of results, whether pagination beyond limit/offset exists, and what a returned order contains. The missing routing against wetaca_orders_show is the most consequential gap.

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 the schema already explains limit, offset, profile and debug, including the same CLI defaults the description repeats. The description compensates for nothing and adds no interpretation of how pagination interacts between limit and offset.

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?

"Pedidos anteriores" plus the CLI equivalence `wetaca orders list` makes clear this returns a list of past orders, so an agent can identify the resource and the general operation. It stops short of an explicit verb like "lista" and never contrasts with the sibling wetaca_orders_show, which also deals with orders.

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 or when-not-to-use guidance: nothing tells the agent why to pick this over wetaca_orders_show for a single order or over wetaca_deliveries_next for upcoming deliveries. Only the parameter defaults are given, which is configuration, not selection guidance.

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