Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_lal_kitab_varsha_pravesh

Read-onlyIdempotent

Retrieves the Lal Kitab Varsha Pravesh annual chart entry for a chosen year using birth details, returning the varshphal year start moment, weekday, and entry chart details.

Instructions

Get the Lal Kitab Varsha Pravesh (annual chart entry) for a chosen year.

Returns the moment the varshphal year begins for the native and the entry chart details. weekday is the day of that moment; 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_lal_kitab_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., '2026')

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that the operation is read-only, idempotent, open-world, and non-destructive. Beyond that, the description explains that the result is the annual-year entry moment plus entry chart details, and clarifies the sunrise-based weekday handling for Varsha Pravesh.

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?

The description is short, front-loaded with the purpose, and structured as purpose, return behavior, and weekday caveat. It is efficient, though the weekday explanation largely duplicates the detailed schema description.

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 chart-entry tool with full schema coverage and an output schema, the description supplies enough context to understand what is returned and how weekday selection works. It does not fully route the agent among sibling varshphal tools, but it is otherwise complete.

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 input schema already documents the birth-detail fields, varshphal_year, and weekday. The description restates the purpose of the chosen year and gives context for weekday='vedic', but adds limited meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the Lal Kitab Varsha Pravesh annual chart entry for a chosen year. It also clarifies that the result includes the moment the varshphal year begins and the entry chart details, making the tool's distinct purpose clear.

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 guidance on when to use this tool versus related varshphal or Lal Kitab chart tools. The intended use is only implied by the phrase 'for a chosen year' and by the resource name, leaving alternative-selection guidance absent.

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