Namaste America

get_indian_restaurants

Find Indian restaurants by location and/or filters.

Provide either a point (`lat`+`lng`, optionally `radius_miles`) or `city`/`state`.
Optional filters: `region_tag` (e.g. "Gujarati", "South Indian"), `dietary_tags`
(any of "vegetarian", "vegan", "halal", "jain"), `tag` (a keyword/dish like "biryani",
"dosa", "catering"), `open_now` (only places open at the current time), `featured_only`.
Use `offset` (e.g. offset=25 after a limit=25 page) to page further; the response's
`has_more` says whether another page exists.

Each record includes a `description`, `tags`, a `confidence_score` (0-1), an `is_featured`
flag, an `open_now` flag (true/false/null), and `distance_miles` when a point was supplied.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No
`lng`	No
`tag`	No
`city`	No
`limit`	No
`state`	No
`offset`	No
`open_now`	No
`region_tag`	No
`dietary_tags`	No
`radius_miles`	No
`featured_only`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 20, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

First observedJul 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description bears full burden for behavioral disclosure. It describes the read-only nature (find restaurants), filtering, pagination, and output fields (description, tags, confidence_score, etc.). Missing details like authorization or rate limits, but the scope is clear and non-misleading.

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 a single paragraph but well-organized with clear, sequential sentences. It avoids fluff and conveys all necessary information efficiently. Minor improvement could be grouping parameter categories into bullet points for easier scanning, but it's already concise and informative.

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 the tool's complexity (12 parameters, 0 required) and the presence of an output schema, the description covers location modes, filters, pagination, and output fields adequately. It implies mutual exclusivity between point and city/state but does not explicitly state constraints like 'do not mix both modes.' Slightly more explicit guidance would make it complete.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description thoroughly explains all key parameters: location modes (lat/lng/radius vs city/state), filters (region_tag with examples, dietary_tags, tag, open_now, featured_only), and pagination (offset, limit, has_more). It adds meaning that the bare schema lacks.

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 starts with 'Find Indian restaurants by location and/or filters,' clearly stating the tool's purpose with specific verb and resource. It distinguishes itself from sibling tools like 'search_restaurants_by_text' by emphasizing structured filters and location modes rather than free-text search.

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 explains when to provide a point (lat/lng with optional radius) or city/state, and covers pagination with offset. However, it does not explicitly state when NOT to use this tool (e.g., when to use search_restaurants_by_text or get_restaurant_details), which would improve differentiation further.

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

All Namaste America tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.