Skip to main content
Glama

Dishes of London

Find a dish in London

find_dishes
Read-onlyIdempotent

Find venues in the covered parts of London that serve a dish, with each matching dish's name, price as printed on the menu, the venue's own diet labels, and the link to the venue's page. Filters: an area name, or a postcode / coordinates with a radius; a maximum price; a diet; and when it is served. Coverage is 7 London boroughs (Camden, City of London, Hackney, Islington, Newham, Tower Hamlets, Waltham Forest), not all of London: call list_coverage for the area names. Diet filters only match labels the venue prints on the dish, never a guess, so check allergies with the venue. Times come from the menu where it prints them; venues that only have opening hours are listed separately as times_not_printed. Prices are as read on the date shown, not live. Read-only. Use get_page with a venue URL for the full menu.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dish": "<dish>"
    },
    "name": "find_dishes"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional: a borough or neighbourhood by name, e.g. "Shoreditch", "Camden Town", "Hackney". Matches venues inside it. Use near instead for a postcode or a point.
dietNoOptional: vegan (also matches "vegan option"), vegetarian (includes vegan), gluten-free (also matches "GF option"), dairy-free, halal. Only labels the venue prints on that dish count.
dishYesThe dish or food in plain words, e.g. "fish and chips", "pulled pork burger", "dosa", "bottomless brunch". Several dishes joined by "and" must all be at the same venue ("wings and chips").
nearNoOptional: a UK postcode ("E8 3RL"), a postcode district ("N1"), or "latitude,longitude". Matches venues within radius_km, nearest first. Postcodes are looked up on postcodes.io.
whenNoOptional, in London time: now = serving at this minute; tonight = from 17:00 today; today / tomorrow = any time that day; breakfast, brunch, lunch, dinner = that window today; a weekday = any time that day.
limitNoVenues to return. Default 10.
max_priceNoOptional: highest price in pounds (GBP) for the dish, e.g. 12. Dishes with no printed price are left out when this is set.
radius_kmNoOnly with near: how far to look, in km. Default 1.5 for a full postcode or a point, 2.5 for a postcode district.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, and the description adds real substance beyond them: coverage is limited to 7 named boroughs rather than all of London, diet filters match only printed venue labels and never a guess, times come from menu data with venues lacking printed times surfaced separately as times_not_printed, and prices are as-read on the capture date rather than live. These are exactly the constraints an agent needs to set expectations and avoid overclaiming results.

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 the core action and return shape, then coverage limits, then caveats, then sibling routing. Dense and mostly waste-free, though the mid-section reads as a run-on list of caveats and could be split for faster scanning.

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 no output schema, the description carries the return contract itself (dish name, printed price, venue labels, venue link) and flags the separate times_not_printed bucket, so an agent knows the shape of a response. For an 8-parameter open-world search with full schema coverage and annotations, nothing material is missing.

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 the parameter docs are already detailed (enum semantics for diet and when, postcode/coordinate handling for near, radius defaults), so the description's restatement of the filters adds little beyond the schema. Baseline 3 is appropriate; the description's contribution here is mostly the return-field enumeration plus the allergy caveat.

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 ('Find venues ... that serve a dish') and enumerates what comes back per match (dish name, printed price, venue diet labels, venue link). It is clearly distinguishable from list_coverage (area names), get_page (full menu), and search_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'call list_coverage for the area names' when choosing an area, and 'use get_page with a venue URL for the full menu' for deeper detail. The near-vs-area split is also called out in the schema. Coverage limits are stated up front so the agent knows when the tool does not apply.

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