Crawlora MCP

swiggy_collections

Read-only

Swiggy (India) curated dish/cuisine collections for a location (e.g. Idli, Biryani, Dosa), each with the id swiggy_search's collection_id param takes.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "swiggy_collections"
  }
}

Input Schema

Name	Required	Description	Default
`latitude`	Yes	Search center latitude (required).
`longitude`	Yes	Search center longitude (required).

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context: results are India-specific and location-scoped, and each collection carries an id consumed downstream. It does not contradict annotations; no return-format detail is needed since an output schema exists.

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?

A single sentence packs the resource, the geographic scope, examples, and the downstream id linkage with no waste. The most decision-relevant facts are front-loaded.

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 an output schema present, return values need not be explained, and the description covers purpose, scope, and integration with swiggy_search. It is nearly complete; only explicit when-to-use-vs-alternative guidance is missing.

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 coverage is 100% with both lat/long parameters fully documented, so the baseline is 3. The description only echoes 'for a location' and adds no syntax, format, or constraint detail beyond the schema.

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 resource ('Swiggy (India) curated dish/cuisine collections') plus the scoping dimension ('for a location') and gives concrete examples (Idli, Biryani, Dosa). It also cross-references swiggy_search's collection_id param, so an agent can distinguish it from siblings like swiggy_restaurant or swiggy_search without opening schemas.

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?

The description implies the workflow: call this to obtain collection ids that swiggy_search consumes via collection_id. That is clear context for why/when to reach for it, but it never explicitly states exclusions or contrasts with sibling tools such as swiggy_search directly.

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?