Skip to main content
Glama

TableJourney food travel

by com.tablejourney
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity slug or name, e.g. 'new-york-city' or 'New York City'. Unknown cities answer with did_you_mean.
limitNoMaximum results (1-100; at most 20 without an API key).
queryNoFree text, e.g. 'cooking class', 'wine tasting', 'market tour'.
countryNoCountry slug or name, e.g. 'italy'. Optional where city is given.
food_onlyNoKeep only products on the site's theme (food and drink, or wine). Set false for everything bookable in the city.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results (1-100)."New value: +"Maximum results (1-100; at most 20 without an API key)."
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. Changed5 schema fields changed
    • 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'."
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), and 'Read-only' simply restates that. The one genuinely new behavioral fact is ranking: relevance-ranked when query is supplied, otherwise popularity-ordered; the enumerated result fields (price, rating, review count, duration, book link) duplicate the output schema and earn no credit.

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?

Usage is front-loaded and the description is short and scannable. However, the second sentence ('Bookable food tours, cooking classes, tastings and tickets for a city') largely re-lists the first sentence's categories, and 'Read-only' repeats an annotation, so a little space is wasted.

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?

With an output schema present, the description correctly does not need to explain return values, and annotations carry the safety profile; it still supplies domain scope, example queries, ranking behavior, and the affiliate/book affordance. What is missing is guidance on the city/country pairing and the role of food_only relative to sibling tools.

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 description coverage is 100%, so the baseline is 3; the description adds meaning by showing that query accepts full descriptive phrases ('a street food tour in Bangkok') and by explaining query's role in ranking. It does not clarify city vs. country precedence, which is left to the schema.

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 names a concrete domain (food tours, cooking classes, tastings, market tours) with sample queries, so an agent can tell this apart from generic sightseeing or event-ticket lookups. It never names a sibling tool explicitly (e.g. things_to_do, tickets), so the differentiation is by domain scope rather than direct routing.

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 an explicit 'Use for ...' clause plus three natural-language examples, giving clear positive usage context. There is no 'when not to use' guidance or pointer to alternatives (things_to_do, tickets, festivals), so the agent must infer boundaries itself.

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 toolsInspect
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