Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_varshphal_basic_astro_details

Read-onlyIdempotent

Retrieve Varshphal basic astrological details and annual chart for a specified year using birth data, with optional weekday calculation for pre-sunrise moments.

Instructions

Get the Varshphal Basic Astro Details (annual chart) for the given year and birth data.

vaar is the weekday of the Varsha Pravesh moment; with weekday='vedic' a moment before sunrise gets the previous day's vaar.

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

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

A3.6/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, and open-world behavior. The description adds useful domain context by explaining that vaar is the weekday of the Varsha Pravesh moment and that vedic weekday counting can roll back before sunrise, which is a nontrivial edge case beyond the safety annotations.

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?

The description is two short sentences with the purpose front-loaded and a focused clarification of the tricky weekday parameter. There is no unnecessary wording.

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 read-only tool with a full output schema, the description covers the core purpose and the most confusing parameter behavior. It is not fully complete because it omits sibling routing and does not clarify what 'Basic Astro Details' includes, but those gaps are modest given the output schema and annotations.

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 varshphal_year, weekday, and all nested birth-detail fields. The description restates the weekday behavior rather than adding new meaning beyond the schema, so the baseline of 3 is appropriate.

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 verb and resource: get Varshphal Basic Astro Details (annual chart) for a given year and birth data. It is clear what the tool returns, but it does not distinguish it from sibling varshphal tools such as horoscope chart or planetary positions.

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?

There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions. The annual-chart context implies usage, but an agent would have to infer why to choose this over the many other varshphal tools.

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