Crawlora MCP

zomato_collections

Read-only

List Zomato's curated city restaurant collections and their URLs, distinct from keyword or geographic search. Use zomato_collection with a returned URL for its restaurant list or zomato_search for search results.

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>"
    },
    "name": "zomato_collections"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	Zomato public city slug, e.g. "mumbai" or "ncr" (the first path segment of a zomato.com city URL).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and scope (openWorldHint=true), so the bar is lower. The description adds that output is curated collections with URLs and that it differs from keyword/geographic search, which is useful behavioral context. It does not describe how many collections are returned or whether results vary by city size, so it stops short of 5.

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?

Three tight sentences: what it does, how it differs from search, and what to do with the output. No filler, and the key distinction is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one required param, annotations that declare read-only/open-world, and an output schema that carries the return shape, the description covers purpose, differentiation, and next-step routing. Nothing an agent needs to select and call this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the city param is fully documented in the schema (including slug examples like 'mumbai' and 'ncr'). The description adds no parameter detail beyond the schema, but since the schema is complete, baseline is met; the description's role here is minimal by design.

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 city restaurant collections and their URLs') and explicitly distinguishes itself from keyword/geographic search. The sibling zomato_search is named as the contrast, so an agent can separate the two without inspecting schemas.

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

Usage Guidelines5/5

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

Explicit routing: it names the follow-up tool ('Use zomato_collection with a returned URL for its restaurant list') and the alternative ('zomato_search for search results'). This tells the agent both what this tool returns and what to call next, which is exactly the when-to-use guidance needed.

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

All Crawlora MCP tools Inspect

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

Need Help?