Skip to main content
Glama

Vedha360

Verse of the day

get_daily_verse
Read-onlyIdempotent

Vedha360's verse of the day — one scripture verse, the same for everyone on a given day — in Sanskrit, transliteration and a translation.

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_daily_verse"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone deciding 'today'Asia/Kolkata
dateNoYYYY-MM-DD within 7 days of today; default today
langNoLanguage of the translation: en, hi, bn, mr, te, ta, gu, kn, ml, or, pa; 'sa' = Sanskrit (Devanāgarī), 'iast' = transliteration.en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, and an output schema exists, so the description carries a lower burden. It adds one genuinely useful behavioral fact — the verse is identical for all callers on a given day, i.e. no personalization — but says nothing about error behavior or the effect of the date window beyond what the schema states.

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 well-formed sentence with the key scope fact ('same for everyone on a given day') front-loaded ahead of the output-format detail. The em-dash aside is slightly cumbersome but nothing is wasted.

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?

All three parameters are optional with defaults, the schema documents them fully, and an output schema covers the return value, so the description's job is limited to stating what the tool returns — which it does, including the three renderings. The only missing piece is guidance on choosing it over the other scripture tools.

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%, with tz, date, and lang each fully documented including the enum values, so the baseline of 3 applies. The description's mention of Sanskrit, transliteration, and translation loosely clarifies the 'sa' vs 'iast' vs translation-language choices, but adds little beyond the schema's own pattern documentation.

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 states a specific resource and behavior: 'verse of the day — one scripture verse, the same for everyone on a given day'. The shared/non-personalized framing implicitly separates it from a general verse lookup like get_verse, but no sibling is named, so the differentiation is inferential rather than explicit.

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 implied by the name and the 'same for everyone on a given day' scope, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as get_verse or search_scripture. An agent must infer that this is the daily-devotional entry point rather than a targeted lookup tool.

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