Namaste America

get_indian_temples

Find Indian-American temples (Hindu/Sikh/Jain places of worship).

Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by
`religion` ("hindu", "sikh", "jain"), `denomination` (e.g. "swaminarayan"), `tag`, or
`open_now`. Records include description, deity, region, tags, hours and `open_now`.

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
`religion`	No
`denomination`	No
`radius_miles`	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

A3.5/5.0

Behavior3/5

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

The description lists returned fields (description, deity, etc.) but does not address behavior when no location is provided, pagination, or ordering.

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 concise and front-loaded with the main purpose. It could be slightly more compact but is efficient overall.

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

Completeness3/5

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

Given the 11 parameters and output schema, the description covers key filters and return contents but misses pagination params and default behavior, making it somewhat incomplete.

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?

The description explains lat+lng as a point and mentions most filter parameters, adding meaning beyond the schema. It omits limit and offset but covers everything else.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool finds Indian-American temples and lists filter options. It distinguishes from general search but does not explicitly differentiate from search_temples_by_text sibling.

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

Usage Guidelines3/5

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

The description explains how to use location or city/state filters, but lacks guidance on when to use this tool versus get_temple_details or search_temples_by_text.

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.