Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_vimshottari_prana

Calculates Vimshottari Prana dasha periods from birth date, time, and location using specified Maha, Antar, Pratyantar, and Sookshma levels for astrological timing analysis.

Instructions

Execute vimshottari_prana AstroChalit API

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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>",
      "hour": "<hour>",
      "minute": "<minute>",
      "second": "<second>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "mahaDasha": "<mahaDasha>",
      "antarDasha": "<antarDasha>",
      "pratyantarDasha": "<pratyantarDasha>",
      "sookshmaDasha": "<sookshmaDasha>"
    },
    "name": "get_vimshottari_prana"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeYesLatitude of birth place
timezoneNoTimezone of birth place (e.g. Asia/Kolkata). Defaults to Asia/Kolkata
longitudeYesLongitude of birth place
mahaDashaYesPlanet name for Maha Dasha
antarDashaYesPlanet name for Antar Dasha
sookshmaDashaYesPlanet name for Sookshma Dasha
pratyantarDashaYesPlanet name for Pratyantar Dasha

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost none of it. It does not state that this is a read-only calculation, what the response contains, whether the dasha planet inputs must be consistent with the birth data, or any error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single four-word sentence with zero waste, but it is under-specified rather than well-sized. Nothing is front-loaded because there is nothing substantive to front-load.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 required parameters, no output schema, and no annotations, the definition should explain what calculation is performed and what the agent gets back. The schema alone tells the agent how to fill parameters but not what the call produces or how it relates to the sibling dasha 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% across all 13 parameters, so birth date/time, coordinates, and the four dasha planet fields are already documented in the schema. The description adds no meaning on top of that, which lands at the baseline for fully covered schemas.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Execute vimshottari_prana AstroChalit API' essentially restates the tool name plus a vendor label. It conveys no resource scope or output concept beyond 'prana', and gives no signal distinguishing it from siblings like get_vimshottari_sookshma or get_vimshottari_pratyantar, which follow the identical naming pattern.

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 when-to-use guidance, no prerequisite statement, and no mention of alternatives. An agent must infer from the name alone that this computes the prana-level dasha and that the other vimshottari_* tools cover the higher dasha levels.

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