TableJourney food travel

Find tours and experiences

experiences

Read-onlyIdempotent

Use for food tours, cooking classes, tastings and market tours in a city: 'a street food tour in Bangkok', 'pasta-making class in Rome', 'wine tasting near Florence'. Bookable food tours, cooking classes, tastings and tickets for a city. Read-only. Each item has price, rating, review count, duration and a tracked book link. Ranked by relevance to query when given, otherwise by popularity.

Input Schema

Name	Required	Description
`city`	Yes	City slug or name, e.g. 'new-york-city' or 'New York City'. Unknown cities answer with did_you_mean.
`limit`	No	Maximum results (1-100; at most 10 without an API key).
`query`	No	Free text, e.g. 'cooking class', 'wine tasting', 'market tour'.
`country`	No	Country slug or name, e.g. 'italy'. Optional where city is given.
`food_only`	No	Keep only products on the site's theme (food and drink, or wine). Set false for everything bookable in the city.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / limit / description

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

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)."

Changed1 schema field changedSep 30, 2026
- addedInput schema / properties / limit / minimum
```
Added value: +1
```

Changed5 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 / food_only / description

Added value: +"Keep only products on the site's theme (food and drink, or wine). Set false for everything bookable in the city."

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

addedInput schema / properties / query / description

Added value: +"Free text, e.g. 'cooking class', 'wine tasting', 'market tour'."

First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description reinforces that while adding useful context about result contents and ranking. The note that results are ranked by relevance to query, otherwise popularity, adds behavioral information beyond the schema and annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with use cases, then quickly covers what is returned, safety, and ranking. It is compact and every sentence contributes useful selection or interpretation guidance.

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?

Given five parameters, full schema coverage, an output schema, and rich annotations, the description provides enough context to select and invoke the tool correctly. It covers the food-focused scope, example queries, result fields, ranking behavior, and read-only nature.

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 100%, so the baseline is 3, but the description adds meaning by explaining that results are ranked by relevance to query when supplied and by popularity otherwise. It does not add much beyond the schema for city, country, limit, or food_only, but the query ranking semantics are helpful.

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 gives a clear verb and resource: finding bookable food tours, cooking classes, tastings, and market tours in a city, with concrete examples. It scopes the tool well, but it does not explicitly distinguish it from broad siblings like things_to_do or tickets, so it falls 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 Guidelines4/5

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

It opens with explicit use cases such as 'a street food tour in Bangkok' and 'pasta-making class in Rome,' which clearly tells an agent when to use this tool. It does not state when not to use it or name alternatives, so it is strong but not complete.

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.