Skip to main content
Glama

Gasthof Koller Daily Menu

get_menu

Get the daily menu (Speiseplan): dishes with prices and the PDF last-updated date.

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": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dishesYesDishes with prices in EUR.
contactYesRestaurant contact details.
currencyYesISO 4217 currency code for all dish prices.
lastUpdatedYesDate the menu PDF was last updated (its creation date), in YYYY-MM-DD format.
kitchenHoursNoKitchen working hours (when dishes are cooked/served), when known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that results include prices and a PDF last-updated date, which hints at freshness, but it does not cover authentication, rate limits, caching, or other operational behavior.

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?

A single front-loaded sentence with no wasted words. The verb and resource appear first, followed by the useful return-content details.

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?

With an output schema and zero parameters, the description provides enough context to call the tool correctly. It could be slightly more complete by stating that this is a safe read-only retrieval, but the core information is present.

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?

There are no parameters, and schema coverage is complete by definition. The description adds no parameter semantics because none are needed, matching the baseline for a zero-parameter tool.

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

Purpose5/5

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

States a specific verb and resource: get the daily menu (Speiseplan). It also identifies the returned contents: dishes, prices, and the PDF last-updated date, so the tool's purpose is immediately clear.

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?

The tool is a simple zero-parameter getter, and 'daily menu' implies when it should be used. However, there is no explicit guidance about alternatives, timing, or exclusions, so usage is only implied.

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