Skip to main content
Glama

diner_guide

Read-onlyIdempotent

Read the complete Byte Byte Diner guide and optional Sharing your visit customs. Read-only; no spending or visit changes. Use {}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "diner_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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=false, so the safety profile is known. The description mostly restates that ('Read-only') but does add domain-specific framing — no spending and no visit-state changes — which tells the agent the guide read has no game consequences. It does not describe what the guide contains or how long it is.

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 resource being read and followed immediately by the behavioral guarantee. Minor deduction: the phrase 'and optional Sharing your visit customs' is awkwardly worded and reads as a fragment, costing a little clarity.

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 zero-parameter, read-only tool with rich annotations and no output schema, the definition covers what is needed: what it reads, that it takes no arguments, and that it mutates nothing. It could say more about the guide's contents/return shape, but that gap is small given the tool's simplicity.

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

Parameters4/5

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

With zero parameters the schema carries no semantic burden, and the description correctly signals that by instructing 'Use {}'. That removes any ambiguity about whether a guide name or section argument is required.

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 names a specific verb and resource: reading the complete Byte Byte Diner guide, plus an optional 'Sharing your visit customs' section. That distinguishes it from action siblings like diner_order, diner_eat or diner_check, though it does not explicitly contrast it with guest_guide. The purpose is clear, but the garbled second clause slightly blurs what exactly is included.

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?

Usage is only implied: an agent can infer this is the orientation/read step before acting at the diner, and 'Use {}' makes clear no arguments are accepted. There is no explicit when-to-use or when-not-to-use statement, and no reference to alternatives such as guest_guide.

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