Skip to main content
Glama

diner_sit

Arrive alone, or choose a counter or booth seat. Omitting seat only arrives.

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

Input Schema

NameRequiredDescriptionDefault
seatNo
entranceNo
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / entrance
      Added value: +{
      +  "enum": [
      +    "short",
      +    "slow"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

C2.4/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, and it discloses almost nothing: it does not say whether this changes state (occupying a seat), whether it is repeatable, what happens if you are already seated, or what the caller receives back. With zero annotation coverage and no output schema, these gaps are significant for a state-transition tool.

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

Conciseness3/5

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

Two short sentences with no filler, which is appropriately sized for a narrow action. But the wording is cryptic rather than economical: 'Arrive alone' and 'only arrives' force the reader to parse intent that a clearer phrasing could have delivered in the same word count.

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 three-parameter mutation-like tool with no annotations and no output schema, the description leaves too much open: no outcome description, no seat-occupancy consequences, no explanation of entrance or requestId, and no relationship to the surrounding diner tools. The seat default is the only behavior it fully pins down.

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% across three parameters, so the description must compensate. It only clarifies `seat` (counter or booth, optional, omission means arrive without choosing), leaving `entrance` (short/slow) and the required `requestId` UUID entirely unexplained — idempotency and the meaning of entrance must be guessed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this is an arrival/seating action and names the seat options (counter, booth), which matches the tool name diner_sit. However, the opening 'Arrive alone' is ambiguous — it is unclear whether 'alone' describes a seating state, a companion absence, or simply the no-seat default — and the sentence pair partially restates itself in 'Omitting seat only arrives.'

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 guidance on when to call this versus diner_check, diner_order, or diner_eat, nor whether sitting is a prerequisite for ordering or eating. The only conditional offered is that omitting seat results in a bare arrival, which is a parameter default rather than usage guidance.

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