Skip to main content
Glama

TableJourney food travel

by com.tablejourney
OverviewDiscussionsAdmin

dishes

Read-onlyIdempotent

Signature dishes of a city and where to eat them (read-only). Each item has a description, the venues resolved to ids and page URLs, and the page to cite; ranked by editorial score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug or name, e.g. 'new-york-city' or 'New York City'. Unknown cities answer with did_you_mean.
limitNoMaximum results (1-100).
queryNoFree text: a dish, ingredient, style or grape.
countryNoCountry slug or name, e.g. 'italy'. Optional where city is given.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / limit / description
      Added value: +"Maximum results (1-100)."
    • addedInput schema / properties / query / description
      Added value: +"Free text: a dish, ingredient, style or grape."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description adds value by disclosing that results are ranked by editorial score, venues are resolved to IDs and page URLs, and each item includes a citation page. These are behavioral and enrichment details beyond the structured fields.

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 two sentences with the primary purpose front-loaded and the output characteristics summarized compactly. 'Read-only' is slightly redundant with the annotations, but it does not meaningfully hurt conciseness.

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, full parameter documentation, and safety annotations, the description covers the essential purpose, ranking basis, and result composition. It is slightly incomplete only in not routing the agent away from overlapping sibling tools like search_places or places.

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 parameters are already documented in the input schema, and the description need not repeat them. The prose does not add extra meaning about city, query, country, or limit beyond what the schema says, keeping this at baseline.

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 identifies a specific resource — signature dishes of a city and their venues — and orients the agent with 'where to eat them' and 'ranked by editorial score.' It does not use an explicit verb like 'list' or compare against sibling tools such as search_places, so sibling differentiation is implicit rather than stated.

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

Usage Guidelines3/5

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

The phrase 'Signature dishes of a city' implies when to call the tool, but there is no explicit when-not-to-use guidance or mention of alternatives among siblings. The query/country parameters hint at broader usage, but exclusions are left to inference.

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