Namaste America

get_indian_services

Find Indian community services (money transfer/remittance, banks, immigration/visa, travel agents, tax/insurance).

Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by `tag`
(e.g. "money-transfer", "immigration", "travel", "tax") or `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
`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

B3.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior fully. It mentions filtering capabilities but omits details like pagination (limit, offset), ordering, rate limits, or what the response contains. The output schema exists but is not described, leaving behavioral gaps.

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 concise: two sentences that front-load purpose and examples. Every sentence adds value without redundancy.

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 9 parameters, no annotations, and an output schema that is not described, the description provides enough to start using the tool but lacks details on pagination, sorting, and response structure. It is minimally complete for a simple finder but not fully sufficient for complex interactions.

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 0%, so the description must add meaning. It explains lat/lng/radius_miles, city, state, tag, and open_now with examples, covering most key parameters. However, limit and offset are not mentioned, and the description does not fully compensate for the missing schema descriptions.

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 community services with specific examples (money transfer, immigration, etc.), making its purpose clear. It differentiates from siblings like get_indian_finance by covering a broader range, but doesn't explicitly contrast with similar broader tools.

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 when to use the tool (by location or filter) but does not provide explicit guidance on when to avoid this tool and use a sibling like search_services_by_text or a specific get_indian_* tool. Usage is implied but not contrasted.

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.