TableJourney food travel

Search verified places

search_places

Read-onlyIdempotent

Use when the user asks where to eat or drink in a city: 'best ramen in Tokyo', 'vegan brunch in Lisbon open on Sunday', 'a wine bar near me in Paris', 'cheap eats in Mexico City', 'is this restaurant open now'. Search verified venues (read-only). Filter by text, city, kind (a topic such as restaurants, cafes, bakeries, markets, street-food, or a group: eat, drink, bake, do), cuisine, dietary, price tier, opening time, or near a coordinate. Results are ranked by relevance then editorial score and carry provenance (source URL, checked_on, open_status), hours, a page URL to cite and a tracked booking link where one exists. Returns at most limit items; an unknown city returns {did_you_mean: [...]} instead of a list.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City slug or name, e.g. 'new-york-city' or 'New York City'. Unknown cities answer with did_you_mean.
`kind`	No	A topic slug (restaurants, cafes, bakeries, markets, street-food...) or a group: eat, drink, bake, do.
`near`	No	'lat,lng' to search around a point; results then sort by distance.
`limit`	No	Maximum results (1-100; at most 20 without an API key).
`query`	No	Free text: a venue name, dish, cuisine, neighbourhood or theme.
`offset`	No	Skip this many results, for paging.
`country`	No	Country slug or name, e.g. 'italy'. Optional where city is given.
`cuisine`	No	Cuisine slug or name, e.g. 'sichuan', 'neapolitan pizza'.
`dietary`	No	vegan, vegetarian, gluten-free, halal, kosher...
`open_at`	No	'now', a weekday and time such as 'sunday 10:00', or an ISO datetime (UTC). Venues with unparseable hours are returned last, flagged.
`radius_km`	No	Radius for near, in km.
`price_tier`	No	The site's tier symbols for the country, e.g. '€€' or '$$$'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results (1-100)."New value: +"Maximum results (1-100; at most 20 without an API key)."

Changed2 schema fields changedSep 30, 2026
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```

Changed12 schema fields changedSep 18, 2026

addedInput schema / properties / city / description

Added value: +"City slug or name, e.g. 'new-york-city' or 'New York City'. Unknown cities answer with did_you_mean."

addedInput schema / properties / country / description

Added value: +"Country slug or name, e.g. 'italy'. Optional where city is given."

addedInput schema / properties / cuisine / description

Added value: +"Cuisine slug or name, e.g. 'sichuan', 'neapolitan pizza'."

addedInput schema / properties / dietary / description

Added value: +"vegan, vegetarian, gluten-free, halal, kosher..."

addedInput schema / properties / kind / description

Added value: +"A topic slug (restaurants, cafes, bakeries, markets, street-food...) or a group: eat, drink, bake, do."

addedInput schema / properties / limit / description
```
Added value: +"Maximum results (1-100)."
```

addedInput schema / properties / near / description

Added value: +"'lat,lng' to search around a point; results then sort by distance."

addedInput schema / properties / offset / description

Added value: +"Skip this many results, for paging."

addedInput schema / properties / open_at / description

Added value: +"'now', a weekday and time such as 'sunday 10:00', or an ISO datetime (UTC). Venues with unparseable hours are returned last, flagged."

addedInput schema / properties / price_tier / description

Added value: +"The site's tier symbols for the country, e.g. '€€' or '$$$'."

addedInput schema / properties / query / description

Added value: +"Free text: a venue name, dish, cuisine, neighbourhood or theme."

addedInput schema / properties / radius_km / description
```
Added value: +"Radius for near, in km."
```

Changed7 schema fields changedSep 18, 2026

addedInput schema / properties / dietary

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Dietary"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

addedInput schema / properties / open_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Open At"
+}

addedInput schema / properties / price_tier

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Price Tier"
+}

addedOutput schema / properties / result / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

removedOutput schema / properties / result / items

Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}

removedOutput schema / properties / result / type
```
Removed value: -"array"
```

First observedSep 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile; the description adds real behavioral context beyond them: ranking order (relevance then editorial score), the provenance fields returned, that venues with unparseable hours are returned last and flagged, the limit cap without an API key, and the did_you_mean fallback instead of a list for unknown cities. These are exactly the edge behaviors an agent needs to plan around.

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 trigger condition and user-utterance examples, then filters, then result shape — a sensible order with no filler sentences. The middle is dense, and the results paragraph is long, but nearly every clause carries information an agent can act on.

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 the description need not explain returns, yet it still characterizes ranking and provenance, and it covers the tricky no-match path. For a 12-parameter, zero-required search tool, nothing material for correct invocation is missing (only the all-empty-arguments case is unaddressed).

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%, so every parameter's meaning, defaults, ranges and examples are already documented in structured data; the prose largely restates them (kind groups, dietary values, price tier, near coordinate). No additional syntax or interaction semantics (e.g. how city+country+near combine) are added beyond the schema.

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 + resource ('Search verified venues') and pins the scope to dining/drinking venues with filters, ranking and provenance. An agent can immediately distinguish it from detail-oriented siblings like `place` or content siblings like `dishes`/`experiences`.

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

Usage Guidelines4/5

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

The opening 'Use when the user asks where to eat or drink in a city' with five concrete example utterances gives superb intent-matching guidance, including the 'is this restaurant open now' case that maps to open_at. It never names an alternative tool (e.g. `place` for a single venue's detail, or `things_to_do` for activities), so routing between siblings is still inferred.

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

All TableJourney food travel 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?