Skip to main content
Glama

Detalle de pedido

wetaca_orders_show
Read-onlyIdempotent

Fetch read-only details for a specific Wetaca order using its numeric ID, so you can inspect or verify the order without changing it.

Instructions

Equivale a wetaca orders show <id>. Detalle de un pedido numérico. Solo lectura.

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": {
      "order_id": "<order_id>"
    },
    "name": "wetaca_orders_show"
  }
}

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.
order_idYesId numérico del pedido.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so 'Solo lectura' merely restates what structured data provides. The only added context is the CLI command mapping, which helps an agent cross-reference CLI docs. Nothing is said about auth/profile requirements, behavior when the order does not exist, or what the returned detail contains.

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?

Three very short sentences with no padding, front-loaded with the CLI equivalence and the core purpose. 'Solo lectura' is mildly redundant against the annotations and title, but the overall size is well matched to a simple read tool.

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 single-record read with a fully documented 3-parameter schema and complete annotations, the definition is adequate to call correctly. However, with no output schema, the description does not hint at the shape or contents of the returned order detail, which is the main 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?

Schema coverage is 100%, with order_id, profile and debug all described in the schema itself. The description reinforces the numeric constraint on order_id ('pedido numérico') but adds no format, range, or example beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb+resource: 'Detalle de un pedido numérico', naming the entity (single order) and its key qualifier (numeric id). The CLI equivalence 'wetaca orders show <id>' further pins down the operation. It does not explicitly distinguish itself from wetaca_orders_list, but the singular/plural contrast is legible from the text.

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?

Usage is only implied: an agent can infer this fetches one order when an id is known, versus listing orders. There is no explicit statement of when to prefer it over wetaca_orders_list or what to do if the id is unknown. 'Solo lectura' describes safety, not selection guidance.

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