bissl - menus in Austria

Search places

search_venues

Read-only

Places to eat and drink: by name, kind, cuisine, map area or nearness, open now, with a menu, serving lunch today.

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

Input Schema

Name	Required	Description
`q`	No	Words to search for among the places: part of a name - "figlm" finds Figlmüller.
`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.
`kind`	No	Its kind as OpenStreetMap tags it: restaurant, fast_food, cafe, bar, pub, biergarten, ice_cream, food_court, bakery or pastry.
`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".
`has_menu`	No	Only places whose menu with prices bissl read.
`open_now`	No	Only places open right now.
`lunch_today`	No	Only places serving a lunch menu today.

Output Schema

Name	Required	Description
`note`	No	Why there is nothing, when there is a reason to say.
`places`	Yes
`cuisine`	No	The cuisine kept to, when one was asked for.
`attribution`	Yes
`total_places`	Yes	Places matching, of which `places` holds `limit` from `offset` on.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedOutput schema / $defs / Place / properties / part_of

Added value: +{
+  "description": "The larger place it is part of, as its own website names it - the hotel, castle or\nclub its restaurant or bar is in: \"Das Schloss an der Eisenstrasse\". Null for none.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 22, 2026

changedOutput schema / $defs / Place / properties / price_level / description

Previous value: -"\"€\" to \"€€€€\" from its menu's prices; null while bissl doesn't know."New value: +"\"€\" to \"€€€€\" from its menu's prices, against places of its kind - a restaurant's\nmains, a café's coffee and cake, a bar's cocktails; null while bissl doesn't know."

First observedOct 17, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and an output schema exists, so the safety and return-shape burdens are covered elsewhere. The description adds nothing behavioral on top: no pagination guidance, no note that omitted filters mean 'everywhere', no hint about the default sort interaction between lat/lon and sort.

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 compact sentence with no wasted words, and the core facets lead. It is grammatically a fragment rather than a front-loaded statement of action, which slightly undercuts clarity but costs nothing in length.

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

Completeness3/5

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

With 13 optional parameters, an output schema, and annotations, the structured data covers most of what an agent needs, so the description is not required to carry return values. Still, for a 13-param filtered search it says nothing about how the filters combine, what happens with no filters, or how sort and lat/lon interact, gaps the schema only partially fills.

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% and each of the 13 parameters carries a detailed description, so the schema does the heavy lifting. The description's facet list (name, kind, cuisine, map area, nearness, open now, menu, lunch today) merely echoes parameters the schema already documents in more depth, adding no syntax or semantics of its own.

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 is a noun fragment listing facets ('Places to eat and drink: by name, kind, cuisine, map area or nearness...') rather than a verb+resource statement, so the agent must infer that this performs a search. It enumerates the filter surface clearly, but does not distinguish itself from the search_dishes or search_lunch_menus siblings, and the 'serving lunch today' facet overlaps directly with search_lunch_menus.

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: the facet list signals 'use this to find places matching these criteria', but there is no explicit when-to-use, no exclusions, and no routing to the alternatives. Given three sibling search tools with overlapping facets (lunch menus in particular), the agent gets no help choosing among them.

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?