Skip to main content
Glama

Vedha360

Yātrā routes

get_yatra_routes
Read-onlyIdempotent

Yātrā (pilgrimage) routes through the sacred geography of the epics — Rāmāyaṇa, Kṛṣṇa, Śiva, Devī and more. Without route_id: every route; with route_id: that route's ordered stops (place, coordinates, scripture, note, linked stories).

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": "get_yatra_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idNoe.g. 'ramayana'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds the two-mode behavior and lists the stop fields (place, coordinates, scripture, note, linked stories), but an output schema exists, so that payload detail is largely redundant and no error/unknown-route_id behavior is described.

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?

Two sentences, no filler: the domain framing comes first and the conditional behavior is front-loaded in the second sentence. Every clause carries information an agent needs.

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?

For a single optional-parameter read tool with full schema coverage and an output schema, the description covers what the tool does in both modes. The only meaningful gap is that it never signals which route identifiers exist or what happens for an unknown route_id.

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 coverage is 100% and the single parameter already carries an example ('ramayana'), so the baseline is 3. The description earns the extra point by explaining the semantic consequence of the parameter — that it switches the response from a route list to that route's ordered stops — which the schema alone does not convey.

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 a specific resource (Yātrā pilgrimage routes) and scopes it to the epic sacred geography, then splits behavior into two clear modes: list-all without route_id, ordered stops with route_id. An agent can tell what it returns in either case. It doesn't explicitly contrast itself with near neighbors like get_temple_town or find_temple_towns, which keeps it from a 5.

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?

Guidance is limited to parameter-mode selection (no route_id = all routes; with route_id = that route's stops), which is implied usage rather than when-to-use-vs-alternative guidance. Nothing says when an agent should reach for this instead of get_temple_town, find_temple_towns, or get_story, even though the pilgrimage/linked-stories overlap makes that a real ambiguity.

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