Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_varshphal_varsha_pravesh

Read-onlyIdempotent

Generate the Varshphal Varsha Pravesh annual chart for a chosen year using birth details, returning the year, age, exact year-start moment, and weekday.

Instructions

Get the Varshphal Varsha Pravesh (annual chart) for the given year and birth data.

Returns varshphal_year, age, varsha_pravesh (the moment the year begins) and weekday; with weekday='vedic' a Varsha Pravesh before sunrise gets the previous day.

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": {
      "varshphal_year": "<varshphal_year>",
      "params": "<params>"
    },
    "name": "divine_get_varshphal_varsha_pravesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesBirth details
weekdayNoHow the weekday (vaar) is counted: 'civil' (default) changes the day at midnight, like a calendar; 'vedic' changes it at local sunrise, so a moment between midnight and sunrise still belongs to the previous day (e.g. 04:30 on a Thursday is Wednesday). Only matters before sunrise.
varshphal_yearYesYear for the annual (varshphal) chart (e.g., '2024')

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description doesn't need to restate safety. It does add value by naming the returned fields (varshphal_year, age, varsha_pravesh, weekday) and the sunrise-boundary rule, though both points largely duplicate the schema's weekday description and an output schema exists.

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 short sentences, front-loaded with purpose followed by the return contract. No filler, though the weekday sentence is near-redundant with the schema text.

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 three-parameter read-only tool with full schema coverage, annotations and an output schema, the description supplies enough to call it correctly. The remaining gap is routing guidance against the many sibling varshphal endpoints.

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%, including a detailed weekday explanation with the 04:30 Thursday example, so the schema does the heavy lifting. The description's restatement of the vedic sunrise rule adds little beyond it, and the nested KundliInput birth fields are left entirely to 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?

States a specific verb and resource ('Get the Varshphal Varsha Pravesh (annual chart)') and names the two inputs that scope it (year and birth data). It reads clearly as the year-beginning chart rather than a general varshphal report, but it never explicitly contrasts itself with close siblings such as divine_get_varshphal_horoscope_chart or the Lal Kitab variant.

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?

No statement of when to choose this over the many other varshphal tools, and no prerequisites or exclusions. The only implicit cue is that it needs a target year plus full birth details, which an agent would infer from the schema anyway.

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