Skip to main content
Glama

Ficha de un plato

wetaca_dish_show
Read-onlyIdempotent

Retrieve a dish's details and ingredients using its slug from the weekly menu list. Read-only lookup for checking Wetaca meal contents.

Instructions

Equivale a wetaca dish show <slug>. Detalle e ingredientes de un plato. El slug sale de wetaca_menu_list. 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": {
      "slug": "<slug>"
    },
    "name": "wetaca_dish_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug del plato, tal como lo devuelve wetaca_menu_list.
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.8/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 fully covered. The description's 'Solo lectura' merely restates readOnlyHint and adds no new behavioral context such as error behavior for unknown slugs or auth requirements. With annotations doing the heavy lifting, this is the minimum-viable level.

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?

Three short sentences, front-loaded with purpose, then provenance of the slug, then the read-only nature. Nothing is padded and no sentence is wasted.

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 read-only single-record tool with full schema coverage and no output schema, the definition covers what it returns conceptually (detail and ingredients) and the required input source. It could say more about the response shape, but nothing essential to invoking 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?

Schema coverage is 100% and each of the three parameters (slug, debug, profile) already carries its own description, including where the slug comes from. The description's note about the slug source duplicates the schema rather than extending it; 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 a specific verb+resource: 'Detalle e ingredientes de un plato', which makes clear this is a single-dish detail lookup rather than a list. The CLI equivalence line ('wetaca dish show <slug>') reinforces the scope. It stops short of explicitly contrasting with the other *_show siblings, but 'dish' plus the slug-based addressing 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 the key prerequisite explicitly: the slug must come from wetaca_menu_list, which tells an agent the call sequence. It offers no explicit exclusions or when-not-to-use guidance, but for a simple detail fetch the context is sufficient.

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