Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

zomato_cities

List Zomato's curated directory of major cities and filter by name or slug. Use it to find valid city values for Zomato search, restaurant, menu, and collection tools.

Instructions

List Zomato's curated directory of major cities. Returns Zomato's own curated directory of major Indian cities -- the discovery source for the city value used by zomato-search, zomato-restaurant, zomato-restaurant-menu, zomato-collections, and zomato-collection. This is Zomato's own "popular locations" directory, not an exhaustive list of every city Zomato serves -- some smaller markets resolve to a real Zomato city page without appearing here. A city slug from a caller's own prior knowledge (a restaurant URL's first path segment) can still be valid even if this endpoint does not return it.

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring match against a city's name or slug. Omit to list every city in the directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden, and it does disclose meaningful traits: the directory is curated/'popular locations' rather than exhaustive, some smaller markets resolve to real city pages without appearing here, and a known slug may still be valid even if absent. It could add return shape or ordering, but coverage of the incompleteness caveat is genuinely useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, but the phrase 'Zomato's own curated/popular locations directory' is restated three times, padding the text. The inclusion caveats earn their place; the repetition does not.

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 no output schema and no annotations, the description adequately explains what the endpoint returns and the important caveat that the list is not exhaustive. A note on response shape or pagination is absent, but for a simple city-listing tool the agent has enough to call it correctly.

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% and the single optional 'q' parameter is fully documented in the schema as a case-insensitive substring match on name or slug. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ('List Zomato's curated directory of major cities') and explicitly distinguishes itself from siblings by naming zomato-search, zomato-restaurant, zomato-restaurant-menu, zomato-collections, and zomato-collection as the consumers of the city value it returns. An agent can tell exactly what this endpoint produces without opening a schema.

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

Usage Guidelines4/5

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

Frames the tool as 'the discovery source for the city value used by' several sibling tools, which tells the agent when to reach for it, and notes that a slug from prior knowledge can be valid without this call. It stops short of an explicit 'call this before X, skip it if Y' rule, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools