Skip to main content
Glama

Search restaurants

search_restaurants
Read-onlyIdempotent

Search the public directory (opt-in venues only) by location, opening status, cuisine, dietary options, declared attributes, ordering channel, declared price level and menu language — whether a guest can pay online through Thmenu and, right now, a free table or an open waitlist (the restaurant graph's channel states). Neutral ranking (AI-K6): distance in 0.5 km bands when near is given → availability (open now first; unknown hours before closed; a venue in holiday mode counts as closed) → profile freshness (owner-verified within 90 days first) → name. Payment to Thmenu never affects order. Cuisine, dietary, price level and other attributes are owner declarations, not verified facts; venues without a declaration are excluded only when an attribute or price filter is used, and venues without coordinates only when near is used. Returns slug, name, city, country, distance_km, is_open_now (serve-time, in the venue's own timezone; null when hours are unknown; false while the venue is in holiday mode), channels (order · reservation · pickup · delivery), declared attributes, freshness and the menu URL. Paginated.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree text over name and description (min 2 chars).
cityNo
nearNoSearch centre. Venues without coordinates are excluded when set.
pageNo
limitNo
channelNoorder = digital ordering at the table; reservation; pickup = takeaway; delivery = venue's own delivery.
countryNoISO 3166-1 alpha-2
cuisineNoAll listed cuisines must be declared by the venue.
dietaryNoOwner declaration, not a certification.
open_nowNoOnly venues open right now in their own timezone; venues with unknown hours are excluded when true.
waitlistNoOnly venues whose waitlist is open now (WAITLIST_AVAILABLE): the reservations switch, which also opens the waitlist, and the venue open now — not in holiday mode.
price_maxNoOwner-declared price level 1–4 (schema.org priceRange "$" … "$$$$"): venues at or below it. Venues that declared no level are excluded when set.
radius_kmNo
attributesNoAny declared attribute token (meals, family, outdoor, accessibility, cuisine, dietary).
menu_languageNoThe menu can be read in this language: it is the menu's source language, or at least 90 % of the guest menu's dish names are translated into it (the restaurant graph's rule).
table_availableNoOnly venues open now with a table that staff marked ready on the live table board (TABLE_AVAILABLE). Venues not using the board are excluded: unknown is not "available".
payment_availableNoOnly venues where a guest can pay online through Thmenu (PAYMENT_AVAILABLE): the venue's online-payment switch is on, online payment through Thmenu works in its country, and the payment provider has not reported the account unable to take payments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payment_available
      Added value: +{
      +  "default": false,
      +  "description": "Only venues where a guest can pay online through Thmenu (PAYMENT_AVAILABLE): the venue's online-payment switch is on, online payment through Thmenu works in its country, and the payment provider has not reported the account unable to take payments.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / cuisine / items / enum
      Previous value: -[
      -  "turkish",
      -  "kebab",
      -  "ottoman",
      -  "anatolian",
      -  "aegean",
      -  "black_sea",
      -  "mediterranean",
      -  "middle_eastern",
      -  "lebanese",
      -  "persian",
      -  "georgian",
      -  "greek",
      -  "balkan",
      -  "romanian",
      -  "polish",
      -  "eastern_european",
      -  "russian",
      -  "italian",
      -  "pizza",
      -  "pasta",
      -  "french",
      -  "spanish",
      -  "tapas",
      -  "portuguese",
      -  "german",
      -  "austrian",
      -  "british",
      -  "irish",
      -  "scandinavian",
      -  "dutch",
      -  "american",
      -  "burger",
      -  "steakhouse",
      -  "bbq",
      -  "tex_mex",
      -  "mexican",
      -  "latin_american",
      -  "brazilian",
      -  "peruvian",
      -  "caribbean",
      -  "japanese",
      -  "sushi",
      -  "ramen",
      -  "chinese",
      -  "korean",
      -  "thai",
      -  "vietnamese",
      -  "indian",
      -  "pakistani",
      -  "indonesian",
      -  "malaysian",
      -  "filipino",
      -  "african",
      -  "ethiopian",
      -  "moroccan",
      -  "seafood",
      -  "grill",
      -  "vegetarian",
      -  "vegan",
      -  "healthy",
      -  "cafe",
      -  "coffee",
      -  "tea_house",
      -  "bakery",
      -  "patisserie",
      -  "dessert",
      -  "ice_cream",
      -  "breakfast_brunch",
      -  "fast_food",
      -  "street_food",
      -  "fusion",
      -  "international",
      -  "fine_dining",
      -  "bistro",
      -  "pub",
      -  "bar",
      -  "wine_bar",
      -  "cocktail_bar",
      -  "juice_bar",
      -  "hotel_restaurant",
      -  "food_court"
      -]New value: +[
      +  "turkish",
      +  "kebab",
      +  "ottoman",
      +  "anatolian",
      +  "aegean",
      +  "black_sea",
      +  "mediterranean",
      +  "middle_eastern",
      +  "lebanese",
      +  "persian",
      +  "georgian",
      +  "greek",
      +  "balkan",
      +  "romanian",
      +  "polish",
      +  "eastern_european",
      +  "russian",
      +  "italian",
      +  "pizza",
      +  "pasta",
      +  "french",
      +  "spanish",
      +  "tapas",
      +  "portuguese",
      +  "german",
      +  "austrian",
      +  "british",
      +  "irish",
      +  "scandinavian",
      +  "dutch",
      +  "american",
      +  "burger",
      +  "steakhouse",
      +  "bbq",
      +  "tex_mex",
      +  "mexican",
      +  "latin_american",
      +  "brazilian",
      +  "peruvian",
      +  "caribbean",
      +  "japanese",
      +  "sushi",
      +  "ramen",
      +  "chinese",
      +  "korean",
      +  "thai",
      +  "vietnamese",
      +  "indian",
      +  "pakistani",
      +  "indonesian",
      +  "malaysian",
      +  "filipino",
      +  "african",
      +  "ethiopian",
      +  "moroccan",
      +  "seafood",
      +  "grill",
      +  "vegetarian",
      +  "vegan",
      +  "healthy",
      +  "cafe",
      +  "coffee",
      +  "tea_house",
      +  "bakery",
      +  "patisserie",
      +  "dessert",
      +  "ice_cream",
      +  "breakfast_brunch",
      +  "fast_food",
      +  "street_food",
      +  "fusion",
      +  "international",
      +  "fine_dining",
      +  "bistro",
      +  "pub",
      +  "bar",
      +  "wine_bar",
      +  "cocktail_bar",
      +  "juice_bar",
      +  "food_court"
      +]
  3. Changed2 schema fields changed
    • addedInput schema / properties / table_available
      Added value: +{
      +  "default": false,
      +  "description": "Only venues open now with a table that staff marked ready on the live table board (TABLE_AVAILABLE). Venues not using the board are excluded: unknown is not \"available\".",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / waitlist
      Added value: +{
      +  "default": false,
      +  "description": "Only venues whose waitlist is open now (WAITLIST_AVAILABLE): the reservations switch, which also opens the waitlist, and the venue open now — not in holiday mode.",
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / menu_language
      Added value: +{
      +  "description": "The menu can be read in this language: it is the menu's source language, or at least 90 % of the guest menu's dish names are translated into it (the restaurant graph's rule).",
      +  "enum": [
      +    "tr",
      +    "en",
      +    "de",
      +    "fr",
      +    "es",
      +    "it",
      +    "nl",
      +    "pt",
      +    "ru",
      +    "ar",
      +    "zh",
      +    "ja",
      +    "ko",
      +    "pl",
      +    "sv",
      +    "da",
      +    "fi",
      +    "no",
      +    "cs",
      +    "hu",
      +    "ro",
      +    "bg",
      +    "el",
      +    "hr",
      +    "sk",
      +    "sl",
      +    "lt",
      +    "lv",
      +    "he",
      +    "fa",
      +    "sw"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / price_max
      Added value: +{
      +  "description": "Owner-declared price level 1–4 (schema.org priceRange \"$\" … \"$$$$\"): venues at or below it. Venues that declared no level are excluded when set.",
      +  "maximum": 4,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  5. First observed

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 and destructiveHint=false, so safety is covered. The description still adds real behavioral context beyond them: the full neutral ranking order (distance bands, availability, profile freshness, name), the explicit statement that payment capability never influences order, and that cuisine/dietary/price are owner declarations rather than verified facts. Offset slightly because time-dependent semantics like holiday mode are repeated in multiple places without clarifying their interaction with pagination or result limits.

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?

Front-loaded with purpose, then filters, ranking, caveats, return shape and pagination — a sensible order for a 17-parameter tool. The writing is dense and em-dash-heavy, and the ranking sentence packs five tie-breakers plus a holiday-mode parenthetical that is restated later, but almost every clause carries decision-relevant information.

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 17-parameter read tool with no output schema, the description does the heavy lifting well: it enumerates the returned fields (slug, name, city, distance_km, is_open_now, channels, attributes, freshness, menu URL) and lists the channel states. Remaining gaps are small — pagination is only one word ("Paginated."), and the default/limit bounds and radius behaviour are left entirely to the schema.

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?

Schema coverage is 76%, so the schema carries most per-field meaning, but the description adds value the schema lacks: the 0.5 km distance banding for `near`, the ordering in which distance and availability are combined, and the rule that missing coordinates or declarations only cause exclusion when the relevant filter is set. It does not explain `radius_km` interaction with `near` (e.g. that radius is meaningless without a centre) or how `q`, `attributes` and `cuisine` combine.

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?

Opens with a specific verb and resource plus scope ("Search the public directory (opt-in venues only)") and enumerates the filterable dimensions, so the agent knows exactly what is being queried. It never names a sibling such as get_restaurant or list_public_menus to contrast list-search against detail-fetch, so differentiation is implied rather than stated.

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 rules are conveyed indirectly through exclusion semantics ("venues without a declaration are excluded only when an attribute or price filter is used, and venues without coordinates only when `near` is used"), which tells the agent what a filter costs. There is no explicit when-to-use-this-vs-alternative guidance, and no mention of when to prefer get_restaurant or get_restaurant_menu after finding a venue.

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