Menu prices
menu_pricesRead-onlyIdempotent
What things cost on restaurant menus in a city: the middle price, and the middle half of prices, of an espresso, a cappuccino, a beer, a glass of wine, a margherita, a burger, a main course, a lunch offer, a cola and a bottle of still water, read from the menus on restaurants', cafes' and bars' own websites, with the number of menus behind each figure, the day they were read and how many prices a hand check found right. Covers 13 European cities so far (Paris, Madrid, Berlin, Milan, Lisbon, Vienna and others); without a city it lists them. Figures are menu prices, not what a bill comes to.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City slug, for example paris or madrid; leave out for the list of cities with prices | |
| context | Yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess. | |
| conversation_id | No | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request. |