Skip to main content
Glama

diner_eat

Eat a previously ordered dish. Nibble courses are served one course per call.

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": {
      "requestId": "<requestId>",
      "orderId": "<orderId>"
    },
    "name": "diner_eat"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that consumption is incremental (one dish per call), but says nothing about whether the dish is removed from the order, what happens if nothing is ordered, error behavior, or how requestId affects idempotency.

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?

Two short sentences, front-loaded with the core action and no filler. Slightly cryptic domain wording ('Nibble courses') costs it the top score, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-consuming mutation with no annotations, no output schema, and undocumented parameters, the description is too thin. An agent must guess at return values, failure modes, and the meaning of requestId before it can call this safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with two required UUID parameters, so the description must compensate and does not. Neither orderId nor requestId is explained; the idempotency role of requestId in particular is left entirely to inference.

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 concrete verb ('Eat') and resource ('a previously ordered dish'), which distinguishes it from diner_order and diner_refill without opening their schemas. It stops short of explicitly naming those siblings as alternatives.

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?

'Previously ordered dish' implies the prerequisite that diner_order must run first, and 'one course per call' implies repeated invocation for multiple courses. Neither is stated as a rule, and no alternative tool is named for other diner actions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources