Namaste America

get_indian_community

Find Indian community organizations & cultural associations (regional samaj/sangam, cultural centers, Indo-American associations).

Provide a point (`lat`+`lng`) or `city`/`state`. Filter by `tag` (e.g. a region like
"telugu", "gujarati", or "association"/"cultural_center").

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
`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.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description only says 'Find', implying a read operation, but does not explicitly state read-only behavior, required permissions, data freshness, pagination behavior, or any other safety or rate-limiting context. This is insufficient for a tool with 9 parameters.

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?

The description is two sentences: the first states the tool's purpose with examples, the second provides usage instructions. Every word adds value, no fluff. It is front-loaded with the core function.

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

Completeness2/5

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

Despite having an output schema and many parameters, the description omits critical usage details like pagination (limit, offset) and spatial filtering (radius_miles, open_now). It also does not mention the output format, though the schema might cover that. For a tool with 9 parameters, the description is incomplete.

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 description adds meaning for 5 out of 9 parameters (lat, lng, city, state, tag) by explaining their purpose and giving examples for tags (e.g., 'telugu', 'gujarati', 'association'). However, it does not mention limit, offset, radius_miles, or open_now, which are significant for search behavior. With 0% schema description coverage, the description should have covered all parameters, but it only partially compensates.

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 clearly states the tool finds Indian community organizations and cultural associations, providing specific examples like regional samaj/sangam, cultural centers, Indo-American associations. The verb 'Find' and resource 'community organizations' are specific, and the tool is easily distinguished from sibling tools focused on temples, restaurants, etc.

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 how to use the tool: provide a lat/lng point or city/state, and filter by tag. It implies this tool is for community organizations, not for other categories like temples or restaurants. However, it does not explicitly state when not to use it or mention alternative tools for different types of Indian places.

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.