Skip to main content
Glama

Vedha360

Get a temple town

get_temple_town
Read-onlyIdempotent

One temple town: introduction, its temples (deity, significance), festivals, best time to visit, how to reach, related stories and yātrās, and sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_temple_town"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTown slug from find_temple_towns, e.g. 'tirupati'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, so the safety profile is fully covered. The description adds the content scope of the response, which is genuinely useful, but says nothing about behavior on an unknown slug or whether missing sections are omitted.

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 tight list of returned sections with zero filler. It is a noun phrase rather than a sentence, but it front-loads the core fact ('One temple town') before the enumeration.

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?

An output schema exists, so return values need not be explained, and annotations cover safety; the remaining gap is routing — how the agent obtains a valid slug and when to prefer this over siblings that expose festivals, stories or yātrās.

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 100% and the single parameter is well documented (max length, example 'tirupati', origin find_temple_towns), so the schema does the work. The description adds no meaning beyond it, which is the expected baseline.

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?

Enumerates precisely what a call returns: introduction, temples with deity and significance, festivals, best time, how to reach, related stories/yātrās, sources. The word 'One' signals single-record retrieval, distinguishing it in spirit from find_temple_towns, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. Nothing tells the agent to first resolve a slug via find_temple_towns, nor how this differs from get_yatra_routes or list_festivals, which overlap with the returned content sections.

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