Skip to main content
Glama
Sign In
ramayana-mcp

ramayana-mcp

by svenkatreddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_verse

Fetch a single Ramayana verse by kanda, sarga, and verse number, returning Sanskrit text with available translations in English, Hindi, and Telugu.

Instructions

Fetch a single verse by kanda, chapter (sarga) and verse number, with Sanskrit and available translations

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": {
      "kanda": "<kanda>",
      "chapter": "<chapter>",
      "verse": "<verse>"
    },
    "name": "get_verse"
  }
}

Input Schema

NameRequiredDescriptionDefault
kandaYesKanda name, e.g. bala_kanda
verseYesVerse number within the sarga
chapterYesSarga (chapter) number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return payload ('Sanskrit and available translations'), which usefully flags that translation coverage may vary. It says nothing about failure behavior for invalid kanda/chapter/verse values, whether numbering is 1-based, or rate limits, so gaps remain.

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?

A single front-loaded sentence with no filler; the lookup keys and returned content are both stated compactly.

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 simple three-parameter read tool with no output schema and no annotations, the description covers the essential who/what/returns. Only minor items are absent, such as error handling on invalid coordinates and the shape of the translations field.

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 description coverage is 100%, so the schema already documents all three parameters, and the baseline is 3. The description adds only the 'chapter (sarga)' equivalence, a small but real clarification for domain terminology.

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?

States a specific verb (Fetch), a specific resource (a single verse), the exact lookup keys (kanda, chapter/sarga, verse number), and what comes back (Sanskrit plus translations). This clearly separates it from list_kandas, get_sarga, search_verses, and verse_of_the_day without needing to name them.

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?

Usage is only implied: the coordinate-based phrasing signals 'use this when you already know the exact verse location.' There is no explicit when-to-use versus search_verses (partial text/unknown location) or verse_of_the_day, and no stated prerequisites.

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

Deploy Server

Other Tools