City facts
city_factsWhat a city index's websites say, compared with every index of the same kind: the share of listed businesses with no web address, only a social profile or their own site; the share of sites that turn an AI crawler away, publish a readable menu, take bookings or orders directly or grade A or B; the share that declare an English version, show prices, link to WhatsApp, show an old copyright year or load a consent manager; the middle visible price and the page weight. Each with its base, rank and medians. Page: https://directindex.org/city/{slug}#sites and https://directindex.org/stats.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Index slug, for example lisbon or berlin-cafes-bars; see list_cities | |
| 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. |