Skip to main content
Glama

Vedha360

Find temple towns

find_temple_towns
Read-onlyIdempotent

Pilgrimage towns of India and Nepal (e.g. Tirupati, Varanasi, Kāñcīpuram): search by town or temple name, state or deity, or find towns near a point. Returns coordinates, main temple and a one-line highlight.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_temple_towns"
  }
}

Input Schema

NameRequiredDescriptionDefault
deityNoe.g. Shiva, Vishnu, Devi
limitNo
queryNoTown or temple name
stateNoIndian state or country region
near_latNo
near_lngNo
radius_kmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds the shape of the result (coordinates, main temple, one-line highlight), though an output schema exists and this is partly redundant; it says nothing about pagination, default result count, or whether multiple filters are combined with AND.

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?

A single tightly packed sentence that front-loads the domain and examples, then lists search modes, then the return shape — no filler. It borders on dense, but every clause carries information.

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?

With 7 all-optional parameters, rich annotations and an output schema, the description covers the main affordances but leaves gaps: it doesn't say filters are combinable, that all parameters are optional with defaults, or what happens with an empty result. Adequate but not complete for a multi-facet search tool.

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 only 43%, and limit, near_lat, near_lng and radius_km carry no schema descriptions. The description partially compensates by describing the 'near a point' mode and mapping query/state/deity to their meanings, but it never mentions limit or radius_km, so several parameters remain undocumented in both places.

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 names the specific resource (pilgrimage/temple towns of India and Nepal) with concrete examples and the facets you can search by, so the agent knows this is a discovery/search tool. It implicitly contrasts with the singular sibling get_temple_town via 'search by town or temple name', but never states that contrast explicitly.

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?

It enumerates the available search modes (name, state, deity, proximity), which implies when the tool is useful, but gives no explicit when-to-use vs. when-not guidance and no pointer to get_temple_town for single-record lookups or to other siblings. Usage has to be inferred from the facet list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources