bissl - menus in Austria

Search lunch menus

search_lunch_menus

Read-only

The lunch menus (Mittagsmenüs) served today - or another day of this week - with every dish and its price, near a point or in a map area; with q, only the lunch dishes matching it ("schnitzel", "suppe").

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Words a dish must match, as people say them, German or English: "schnitzel", "vegan curry", "glutenfreie pizza". A diet, allergens or a cuisine among them are taken as filters; misspelt German words are put right when that finds something.
`day`	No	"2026-10-20": another day of this lunch week, Monday to Sunday (at the weekend, the coming week's too). Today when left out; open_now only counts today.
`lat`	No	The latitude of a point - the user's, or one they name - to measure distances from and sort nearest first; with `lon`.
`lon`	No	The longitude of that point; with `lat`.
`bbox`	No	Keep to a map area: "west,south,east,north" in degrees - a town, a district, the streets around a place. Everywhere when left out.
`diet`	No	Only dishes of this diet: vegan, or vegetarian (vegan dishes included).
`lang`	No	The language of dish names, descriptions and section titles: de, the menus' own, or en, as bissl translated them.
`sort`	No	The order of the places.
`limit`	No	Places to answer with: 1 to 30, 10 when left out.
`offset`	No	Places to skip, for the next ones: 0 when left out.
`cuisine`	No	Only at places of this cuisine, as OpenStreetMap names it: "italian", "vietnamese".
`free_of`	No	Only dishes whose menu lists their allergens and none of these letters: "A" gluten, "G" milk, "AG" both.
`open_now`	No	Only places open right now.
`max_price`	No	Only dishes costing at most this much, in whole euros.
`min_price`	No	Only dishes costing at least this much, in whole euros.

Output Schema

TableJSON Schema

Name	Required	Description
`day`	Yes	The day the lunch menus are for.
`diet`	No	The filters in effect, asked for or taken from the words.
`note`	No	Why there is nothing, when there is a reason to say.
`places`	Yes	Each with its whole lunch that day - the dishes matching `q`, when it was given.
`cuisine`	No
`free_of`	No
`searched`	No	The words the dishes match, once a diet, allergens or a cuisine among them were taken as filters; null for none.
`corrected`	No	The words put right when they found nothing as typed: "schnitzel" for "schnitzl".
`attribution`	Yes
`total_dishes`	Yes
`total_places`	Yes	Places serving lunch and their dishes, of which `places` holds `limit` from `offset` on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and delivers: it discloses the geographic scoping modes (near a point vs. map area), the temporal scope (today or any day of this lunch week), and that queried dishes come back with prices. It adds genuine operational context beyond the safety profile, though it does not describe pagination behavior or result volume.

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?

A single front-loaded sentence that opens with the resource and its contents before adding the optional narrowing behavior of `q`. Every clause earns its place; the only minor cost is that cramming return content, geo modes, and query semantics into one sentence slightly blurs the structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% schema description coverage on all 15 parameters, the description need not explain return values or field formats. It complements the structured data by explaining the day/geo/query framing, leaving no functional gap an agent needs to fill before calling.

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

Parameters3/5

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

Schema description coverage is 100% across 15 parameters, so the schema already defines q, day, lat/lon, bbox, diet, sort, prices, and the rest in detail. The description only gestures at the point/map-area dichotomy and the q filter, adding framing rather than new parameter meaning. Baseline 3 is correct when the schema does the heavy lifting.

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 concrete resource and its payload: "The lunch menus (Mittagsmenüs) served today ... with every dish and its price, near a point or in a map area." An agent immediately knows this returns venue-level lunch menus with dishes, not a single venue or a dish list. It never names the sibling tools (search_dishes, search_venues) to draw the boundary explicitly, so it stops short of a 5.

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 implied rather than stated: the day parameter is framed as "today - or another day of this week" and `q` is framed as narrowing to matching lunch dishes, which hints at when this tool is appropriate. However, there is no explicit guidance on when to pick this over search_dishes or search_venues, and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bissl - menus in Austria tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?