Get venue menus
get_venue_menusThe menus Dim Hour holds for one venue, with the source and date of each. status is verified (menus read from the venue's own site, with sections and prices), link_only (a menu link from the catalog that nobody has verified), no_link, or unavailable. A link_only answer proves nothing about what the menu says. Each menu carries verified_at and a freshness state; past 90 days it is stale, and with no date it is unknown, never fresh. completeness says whether every menu this venue is expected to have is verified; requirements_unknown means nobody has recorded which menus to expect. At most 300 menu items are returned per call; truncated counts the rest. Prices and dishes change: confirm with the venue before relying on them.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"city": "<city>",
"id": "<id>"
},
"name": "get_venue_menus"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Venue id from search_venues | |
| city | Yes | City name or key | |
| type | No | Only this menu type, e.g. dinner, brunch, cocktails, wine |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| url | Yes | ||
| city | Yes | ||
| link | No | ||
| name | Yes | ||
| menus | Yes | ||
| status | Yes | ||
| address | Yes | ||
| reasons | Yes | ||
| receipt | Yes | ||
| city_name | Yes | ||
| truncated | No | ||
| snapshot_id | Yes | ||
| completeness | Yes | ||
| requirements | No | ||
| applicability | Yes | ||
| missing_types | Yes | ||
| fresh_complete | Yes | ||
| policy_version | Yes | ||
| stale_after_days | Yes |