Skip to main content
Glama

Próximas entregas

wetaca_deliveries_next
Read-onlyIdempotent

Retrieve the next Wetaca deliveries, including suggestions and pending orders with cancellation IDs, and flag any pending payment that must be completed on wetaca.com. Read-only.

Instructions

Equivale a wetaca deliveries next. Sugerencias y pedidos pendientes, con los ids que usan wetaca_orders_cancel. Si nextPaymentPendingOrder no es null, hay un pago pendiente: este servidor no lo cobra; se paga en wetaca.com. 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_deliveries_next"
  }
}

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

A3.6/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 the safety profile is covered. The description adds genuinely new behavior: the ids returned are the ones consumed by wetaca_orders_cancel, and when nextPaymentPendingOrder is non-null there is an outstanding payment that this server will not charge (payment happens on wetaca.com). That is exactly the kind of side-effect boundary an agent cannot get from annotations.

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?

Four short clauses, front-loaded with the CLI equivalence, and no filler sentences. But it reads as a set of terse fragments rather than a structured statement, and the CLI-equivalence clause is only useful to an agent that already knows the CLI, slightly diluting the lead position.

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?

There is no output schema, so the description carries the reporting burden, and it does name the key response field (nextPaymentPendingOrder) plus the kind of records returned. For a two-parameter, zero-required read tool, that is nearly sufficient; a brief note on result shape or empty-list behavior would close the remaining 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?

Both parameters (debug, profile) are fully documented in the schema at 100% coverage, so no compensation is required. The description adds nothing about parameter meaning, so the baseline of 3 applies.

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?

The description names the concrete content returned ('Sugerencias y pedidos pendientes') and anchors the tool to the CLI equivalent 'wetaca deliveries next', so an agent knows this is the retrieval of upcoming deliveries. It stops short of an explicit verb and never contrasts with the nearby wetaca_deliveries_options/set_option siblings, so the distinctions still need inference.

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?

It does give real routing value by tying this tool to wetaca_orders_cancel ('con los ids que usan wetaca_orders_cancel'), which tells the agent how this output feeds a later call. However, there is no explicit statement of when to choose this over wetaca_deliveries_options or wetaca_orders_list, and no exclusions.

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