Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

swiggy_restaurant

Fetch a Swiggy restaurant's full profile by id—name, address, cuisines, cost for two, ratings, delivery time, weekly hours, open/closed status, and current promotions.

Instructions

Get one Swiggy restaurant's detail. Returns one Swiggy restaurant's detail by id: name, city, area, address, postal code, coordinates, phone, cuisines, cost for two, rating and total rating count, delivery time, weekly opening hours with the current open/closed callout, plus the promotions Swiggy currently shows on that restaurant's page (headline discount, conditions, and coupon code when one is needed). Swiggy has no lighter restaurant-detail-only source -- this reads the same upstream as /swiggy/restaurant/menu, just without the menu items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesCaller latitude (required by Swiggy's own menu API)
longitudeYesCaller longitude (required by Swiggy's own menu API)
restaurant_idYesRestaurant id, from /swiggy/search's id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses what is returned (including live open/closed callout and current promotions) and that it reads the same upstream as /swiggy/restaurant/menu without menu data. It does not explicitly say read-only/auth/rate limits, but 'Get' and the non-mutating context make the operational behavior sufficiently clear.

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?

Front-loaded with 'Get one Swiggy restaurant's detail' then a detailed but efficient field list. The long second sentence earns its place because no output schema exists and the field enumeration is essential context, with no filler.

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?

Complete for a single-record detail tool without an output schema. It lists the full set of return fields including promotions and open/closed status, and also clarifies the source relationship to the menu endpoint, giving an agent everything needed to invoke 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 coverage is 100%, so the schema already documents all three parameters. The description says 'by id' but adds no extra meaning beyond the schema's property descriptions. Baseline 3 is appropriate.

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 ('Get') and resource ('one Swiggy restaurant's detail'), enumerates the returned fields, and differentiates from swiggy_restaurant_menu by explaining it reads the same upstream without menu items. An agent can clearly distinguish this tool from its siblings.

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?

Provides clear context: it is the go-to source for restaurant detail-only and shares upstream with /swiggy/restaurant/menu without menu items. This strongly implies when to use it vs the menu variant, but it doesn't explicitly state 'use swiggy_restaurant_menu when menu items are needed.'

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