Skip to main content
Glama

Ver menú de la semana

wetaca_suggestion_show
Read-onlyIdempotent

Show next week's Wetaca menu for a profile, including prices, delivery window, and the profileSuggestionId/productId needed to edit the suggestion. Read-only.

Instructions

Equivale a wetaca suggestion show. Menú de la próxima semana por perfil: precios, ventana de entrega y los ids (profileSuggestionId, productId) que hacen falta para wetaca_suggestion_edit. 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_suggestion_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/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 the safety profile carries little weight in the description. What the description adds beyond that is the return payload (prices, delivery window, ids), which matters because there is no output schema. "Solo lectura" merely restates the annotation, and nothing is said about per-profile scoping failures or error behavior.

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

Conciseness5/5

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

Two short sentences, front-loaded with the CLI equivalent and the core resource, then the payload and the read-only constraint. No filler, and every clause carries information an agent can act on.

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?

For a two-optional-parameter read tool with no output schema, the description covers purpose, payload contents, and the follow-up tool, which is enough to call it correctly. It stops short of describing failure behavior or the scope of "próxima semana" relative to the profile, so it is not fully complete.

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%, with both the profile and debug parameters fully documented in the schema, including the default-profile fallback and what debug writes to stderr. The description adds no parameter-level 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 specific resource and scope ("Menú de la próxima semana por perfil") and enumerates what it contains: prices, delivery window, and the profileSuggestionId/productId identifiers. It also anchors the tool to its CLI equivalent and separates it from wetaca_suggestion_edit, which consumes those ids. The only gap is that it doesn't distinguish itself from the other menu-listing sibling, wetaca_menu_list.

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?

Usage is clearly implied by stating that the ids it returns are exactly what wetaca_suggestion_edit needs, so an agent can infer the read-then-edit workflow. It also rules out mutation with "Solo lectura." There is no explicit when-not-to-use statement, which keeps it below a 5.

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