DivineAI

Vrat dates

get_vrat_guide

Read-onlyIdempotent

Which vrats (fasts) fall on which dates: Ekadashi, Pradosh, Purnima, Amavasya, Karwa Chauth and others, with the deity, from DharmikVibes' verified festival calendar and DivineAI's vrat list. How a vrat is kept is included only once a scholar has checked that text.

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

Input Schema

Name	Required	Description
`vrat`	No	Only this vrat, for example Ekadashi, Pradosh, Karwa Chauth, Purnima. Omit for all.
`to_date`	No	ISO end date. Omit for 60 days after the start.
`from_date`	No	ISO start date. Omit for today in India.
`include_weekly`	No	Also list the weekday vrats (Somvar, Mangalvar, ...).

Output Schema

Name	Required	Description
`note`	No
`count`	Yes
`vrats`	Yes
`window_to`	Yes	The answer covers no further than this date
`health_note`	Yes	Shown with every vrat answer
`window_from`	Yes
`open_in_divineai`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/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 safety is covered. The description adds genuinely new behavioral context: the data provenance (DharmikVibes verified calendar, DivineAI vrat list) and the caveat that ritual-procedure text appears only after scholar verification, telling the agent to expect partial detail.

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?

Two sentences, front-loaded with the core resource and its fields before the provenance and caveat sentences. The source-branding phrasing ('DharmikVibes', 'DivineAI') is slightly promotional but does carry informational weight about reliability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape needn't be explained, and the schema fully documents all four params. What remains for the description — what data is returned, how trustworthy it is, and that ritual instructions are conditional — is all present.

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%, documenting the vrat filter, ISO from_date/to_date, the 60-day default window and include_weekly. The description adds nothing about parameters beyond the schema, so the baseline of 3 applies.

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?

States a specific verb+resource: it returns which vrats (fasts) fall on which dates, naming concrete examples (Ekadashi, Pradosh, Karwa Chauth) plus the deity field. It does not, however, say how this differs from get_festival_dates, which plausibly also returns dated observances, so sibling differentiation is left to inference.

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?

The description implies the use case (queries about vrat dates) but gives no explicit when-to-use/when-not and never references the two siblings, get_festival_dates and get_panchang. With a probable overlap between vrats and festivals, the absence of routing guidance is a real gap.

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

All DivineAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?