Find Indian yoga & cultural studios (yoga, classical dance, music, language classes).
Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by `tag`
(e.g. "yoga", "bharatanatyam", "kathak", "tabla", "carnatic") or `open_now`.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | ||
| lng | No | ||
| tag | No | ||
| city | No | ||
| limit | No | ||
| state | No | ||
| offset | No | ||
| open_now | No | ||
| radius_miles | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "title": "Offset",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It correctly implies a read operation (find) but does not disclose default limits (limit=25, offset=0, radius=15), pagination behavior, or any potential side effects. The description is adequate but lacks detailed behavioral context for a tool with 9 parameters and no annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. The first sentence front-loads the purpose and scope, making it immediately clear what the tool does. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (9 parameters, no required ones) and that an output schema exists, the description covers the most important usage aspects: location-based and tag-based filtering. It does not mention pagination parameters (limit, offset) or default radius, but the schema and output schema likely cover the rest. It is complete enough for most use cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain the parameters. It successfully does so: explains lat/lng as a point, radius_miles as optional, city/state as alternatives, tag with examples, and open_now as a boolean filter. It does not explain limit/offset, but those are common pagination parameters. Overall, it adds significant meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Find' and the specific resource 'Indian yoga & cultural studios', listing examples like yoga, classical dance, music, language classes. This distinguishes it from siblings such as search_studios_by_text, which likely performs a text-based search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage patterns: 'Provide a point (lat+lng, optional radius_miles) or city/state. Filter by tag... or open_now.' This tells the agent when to use this tool (location-based or tag-filtered queries) but does not explicitly state when not to use it or mention alternatives like search_studios_by_text.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.