Namaste America

get_indian_events

Find upcoming Indian-American community events (festivals, garba, concerts, puja).

Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by
`category` ("festival", "garba", "concert", "puja", …) or `tag` ("diwali", "holi", …).
Returns UPCOMING events by default (soonest first); set `include_past=true` for history.
Each event has `start_at`/`end_at`, venue, category and a description. Use `offset` to page
(the response's `has_more` says whether another page exists).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No
`lng`	No
`tag`	No
`city`	No
`limit`	No
`state`	No
`offset`	No
`category`	No
`include_past`	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

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries full burden and covers key behaviors: default upcoming ordering, include_past for history, offset pagination with has_more, and output fields. Lacks details on error handling or rate limits but is sufficient for safe usage.

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 (around 100 words) and front-loads the purpose. Although not bullet-pointed, it efficiently conveys parameter groupings and behavior constraints without redundancy.

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 complexity (10 parameters, no annotations) and existence of an output schema, the description covers most usage aspects: default ordering, pagination, output fields, and filter examples. Minor gaps include not clarifying that lat/lng are required together and omitting 'limit' explanation.

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?

Schema description coverage is 0%, but the description adds meaning for 9 of 10 parameters (missing 'limit'), grouping them logically and providing examples for enums. It explains the location vs. filter distinction and default behavior.

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 upcoming Indian-American community events using specific verbs and resource. It distinguishes itself from siblings like search_events_by_text and get_event_details by focusing on location, category, and tag filters.

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 implies usage context through parameter options (location vs. city/state, filters) but does not explicitly state when to use this tool over other event-related tools (e.g., search_events_by_text for text search, get_event_details for a single event).

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.