Skip to main content
Glama

Carta de la semana

wetaca_menu_list
Read-onlyIdempotent

Lists the weekly Wetaca menu dishes with their IDs so you can build the --set for editing a suggestion. Optionally pass a zipcode; read-only.

Instructions

Equivale a wetaca menu list. Platos de la semana y sus ids, para construir el --set de wetaca_suggestion_edit. zipcode es opcional. 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_menu_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.
zipcodeNoCódigo postal (--zipcode). Si falta, el CLI usa el de la cuenta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. 'Solo lectura' merely restates readOnlyHint and 'zipcode es opcional' restates the schema's own fallback note; nothing is added about auth, rate limits, or whether the menu changes during the week.

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 short sentences, front-loaded with what the tool returns and what it feeds into. Minor waste: 'Solo lectura' duplicates the annotations and the CLI-equivalence note carries little weight once the resource is described.

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 simple, zero-required-parameter read with no output schema, the description usefully discloses that the return is dishes with ids, which the schema cannot convey. Nothing an agent needs in order to call it correctly 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?

With 100% schema description coverage, the schema already explains debug, profile and the zipcode fallback to the account's postcode. The description only echoes that zipcode is optional and never mentions profile or debug, so it adds no meaning beyond structured data. Baseline 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?

States the resource precisely: the week's dishes plus their ids, and names its consumer (the --set for wetaca_suggestion_edit). An agent can tell this is a read of the weekly menu, not of orders, addresses or profiles. No explicit leading verb, but the effect is unambiguous.

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?

Gives a concrete downstream use — build the --set argument for wetaca_suggestion_edit — which effectively tells the agent when to reach for it. It does not name an exclusion or alternative (e.g. wetaca_dish_show for one dish), so it stops short of full routing guidance.

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