Skip to main content
Glama
Sign In
ramayana-mcp

ramayana-mcp

by svenkatreddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

verse_of_the_day

Retrieve a deterministic Ramayana verse for any calendar date; the same date always returns the same verse, chosen uniformly from the full corpus.

Instructions

A deterministic verse of the day: the same calendar date always yields the same verse, drawn uniformly from the whole corpus

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD; defaults to today (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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 usefully discloses determinism (same date always yields the same verse) and the uniform distribution across the corpus, which implies idempotency and a read-only operation. It omits error behavior for invalid dates, auth requirements, and the return format.

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?

One compact sentence, front-loaded with the core purpose and immediately followed by the behavioral guarantee. No wasted words.

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 zero-required-parameter read tool with no output schema, the description covers the essentials: what is returned and the determinism guarantee. Only minor gaps remain around return shape and failure modes for malformed dates.

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 date parameter is fully documented in the schema (format, default to today UTC). The description alludes to the date driving the output but adds no format or edge-case detail beyond the schema.

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 (verse of the day) and its defining property (deterministic, uniform draw from the corpus). It is clearly distinct from siblings like get_verse and search_verses, though it never names them 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?

Usage is only implied by the phrase 'verse of the day' — an agent can infer the daily-devotional use case. There is no explicit when-to-use statement and no routing guidance versus get_verse or search_verses.

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