Skip to main content
Glama

diner_check

Read the receipt for this visit. Asking is optional.

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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden. "Read" implies a non-mutating call, but the description never states that this is side-effect free, whether it costs anything, whether it can fail outside a diner visit, or what it returns. "Asking is optional" is opaque phrasing that does not disclose behavior.

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?

It is short and front-loads the action, which is good, but the second sentence is cryptic filler that does not earn its place and actively invites misreading.

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 one-parameter tool with no annotations and no output schema, the description should at minimum say what comes back and what requestId refers to. Both are absent, so the agent cannot predict the result shape or safely construct the call.

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?

There is one required parameter (requestId, a UUID) with 0% schema description coverage, and the description says nothing about it. The agent is left to infer that requestId identifies the diner session being receipted, which is a guess rather than documented semantics.

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?

"Read the receipt for this visit" gives a verb and an object, so the agent can guess this returns the bill/charges for the current diner session. But "receipt" is metaphorical and the second sentence ("Asking is optional") adds no clarity about what is actually retrieved, so it is only marginally distinguishable from siblings like diner_order or diner_menu.

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?

The only usage context is "for this visit", with no statement of when the call is appropriate, when it is not, or which sibling to use instead for ordering, refilling, or leaving. "Asking is optional" is unexplained and could be read either as a permission or a hint at another mechanic.

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