Skip to main content
Glama

diner_order

Order one diner item. Its full price is paid immediately.

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>",
      "itemId": "<itemId>"
    },
    "name": "diner_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
usualNo
itemIdYes
requestIdYes
memoryRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / memoryRevision
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / usual
      Added value: +{
      +  "const": true,
      +  "type": "boolean"
      +}
  2. Added

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose the single most consequential trait: the item's full price is charged immediately at order time. It says nothing about whether the order is idempotent, what happens on insufficient funds, whether the item is consumed or merely acquired, or what the response contains. That leaves meaningful mutation behavior undisclosed.

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 sentences, eleven words, zero filler, with the payment consequence front-loaded right after the action. Nothing is redundant or padded. Brevity is not the problem here; the missing content belongs to other dimensions.

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 four-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the description is far too thin. The agent knows it will be charged but not what requestId is for, what "usual" means, or what it receives back. The complexity of the signature demands substantially more explanation than two sentences.

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% against four parameters, so the description is expected to compensate and instead says nothing about any of them. requestId (a uuid, strongly implying idempotent retry semantics), itemId, the const-true "usual" flag, and memoryRevision are all left undefined in prose. The mention of paying "full price" is only faintly related to itemId and does not explain any parameter's meaning or format.

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 pairs a specific verb ("Order") with a specific resource ("one diner item") and adds a scope limit of a single item, so an agent knows exactly what the call does. It stops short of distinguishing itself from nearby siblings like diner_eat, diner_refill, or diner_menu, so a reader cannot tell from the text alone whether ordering also consumes the item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no named alternative. Given siblings such as diner_eat, diner_refill, and diner_menu all plausibly interact with diner items, the absence of any routing hint is a real gap. The only implicit signal is that ordering is a prerequisite to eating.

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