Skip to main content
Glama

TableJourney food travel

by com.tablejourney
OverviewDiscussionsAdmin

Plan a food day in a city

plan_day
Read-onlyIdempotent

Use when the user wants a day planned: 'plan a food day in Paris on Saturday', 'where should I have breakfast, lunch and dinner in Seville'. Compose a food day for one city (read-only): one best-scored open venue per slot from morning to evening, filtered by neighbourhood, dietary need and price tier, every stop open on the given date, plus one bookable experience. Also lists the titles of the editorial itineraries for the city, which are the better plan when one exists (fetch them with itineraries).

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.
dateNoISO date, e.g. '2026-09-20'. Each stop is checked open at its slot time on that weekday.
countryYesCountry slug or name, e.g. 'italy'. Optional where city is given.
dietaryNovegan, vegetarian, gluten-free, halal, kosher...
price_tierNoThe site's tier symbols for the country, e.g. '€€' or '$$$'.
neighborhoodNoNeighbourhood name or slug to keep the day inside.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / date / description
      Added value: +"ISO date, e.g. '2026-09-20'. Each stop is checked open at its slot time on that weekday."
    • addedInput schema / properties / dietary / description
      Added value: +"vegan, vegetarian, gluten-free, halal, kosher..."
    • addedInput schema / properties / neighborhood / description
      Added value: +"Neighbourhood name or slug to keep the day inside."
    • addedInput schema / properties / price_tier / description
      Added value: +"The site's tier symbols for the country, e.g. '€€' or '$$$'."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces 'read-only' while adding substantial context the annotations cannot: every stop is checked open at its slot time on the given date, filtering is by neighbourhood/dietary/price tier, and the result includes a bookable experience plus itinerary titles.

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?

Front-loaded with the activation condition and examples, then the output contract and the sibling handoff. Dense but every clause carries a distinct fact; there is no filler or repetition.

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 and does so fully: per-slot venues, date-validity checking, one bookable experience, and the list of editorial itinerary titles. Nothing an agent needs to call or interpret this tool 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%, so the baseline is 3. The description restates the filter concepts (neighbourhood, dietary need, price tier) but adds no syntax, format, or defaulting detail beyond what the schema fields already document.

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 ('Compose a food day for one city') and spells out the output shape: one best-scored open venue per slot from morning to evening, plus one bookable experience. It also distinguishes itself from the sibling `itineraries`, which an agent can route to without opening either schema.

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?

Opens with an explicit trigger ('Use when the user wants a day planned') followed by two concrete user utterances. It goes further and names the alternative: editorial itineraries are 'the better plan when one exists', with the exact sibling to fetch them (`itineraries`).

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