Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

swiggy_collections

List Swiggy's curated dish and cuisine collections for a latitude/longitude, returning collection IDs for browsing and a coverage flag for delivery availability.

Instructions

List Swiggy's curated collections for a location. Returns the curated dish/cuisine collections Swiggy's own homepage surfaces for a latitude/longitude (e.g. "Idli", "Biryani", "Dosa"). Each collection's id is the value /swiggy/search's collection_id param takes to browse restaurants within it. The response also carries is_serviceable, which says whether Swiggy delivers to the requested coordinates at all: false means the coordinates are outside Swiggy's delivery coverage, so the empty collections list is a coverage answer rather than a location that simply has no curated collections.

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

NameRequiredDescriptionDefault
latitudeYesSearch center latitude
longitudeYesSearch center longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description takes on the burden of behavioral disclosure. It goes beyond the schema by explaining the is_serviceable field and the nuanced interpretation of an empty list (it can be a coverage answer rather than a genuine lack of collections). This gives the agent essential behavioral context, though it doesn't explicitly mention read-only or rate limits, which are less critical for a list endpoint.

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

Conciseness4/5

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

The description is compact, with the main purpose front-loaded in the first sentence. The second sentence adds why this tool is used (identifying collection ids for swiggy_search), and the third addresses an important edge case. Each sentence contributes to understanding the tool, so the length is justified.

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?

Given there is no output schema, the description does a solid job of covering the main aspects: the return type (curated collections), an important field (is_serviceable), and the behavioral nuance around empty results. It also ties into the downstream search tool. It stops short of describing the full object structure of a collection (e.g., id and name), but that level of detail is not strictly required for selection and invocation.

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?

The input schema already provides complete coverage for the two parameters, latitude and longitude, with matching descriptions. The tool description only restates that it takes a latitude/longitude, adding no additional semantics such as format, range, or required precision. With 100% schema coverage, the baseline of 3 is appropriate; the description doesn't add meaning beyond what the schema provides.

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?

The description opens with a clear imperative verb 'List' and identifies a specific resource ('Swiggy's curated collections') with a clear location scope (latitude/longitude). It differentiates the tool from swiggy_search by explaining that collection ids feed into swiggy_search's collection_id parameter, and it gives concrete examples of what the collections are. This is more than a mere restatement of the name; it lets an agent know exactly what the tool returns and how it relates to a sibling.

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 usage context: you need to retrieve curated collections for a location before browsing restaurants within a collection, and it explicitly routes the agent to swiggy_search for that next step. It doesn't explicitly state 'when not to use' the tool versus alternatives, but it does communicate a clear use case and connects to a sibling. This is above the threshold of mere 'clear context, no exclusions'.

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