Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Dashas: Vimshottari Antardasha

astroway_vedic_dashas_vimshottari_antar
Read-onlyIdempotent

Identifies the active Vimshottari Mahadasha for a birth chart at a target date and returns its nine Antardasha sub-periods with their calculated durations.

Instructions

Antardasha (sub-period) within the running Mahadasha. Identifies which MD is active at targetDate (default today UTC), then returns the 9 ADs covering that MD. Sub-period of planet Q within MD of P: years = (P.years × Q.years) / 120.

[Group: Vedic] [Endpoint: POST /v1/vedic/dashas/vimshottari/antar] [Cost: 20 credits (Tier 2)]

Input Schema

NameRequiredDescriptionDefault
bodyYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.

Output Schema

NameRequiredDescriptionDefault
levelNo
systemNo
initialNo
periodsNo
ayanamsaNo
nakshatraNo
currentMahaNo
moonSiderealLongitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description's extra value is the behavioral detail: which MD is selected, that targetDate defaults to today UTC, and that exactly 9 ADs are returned. It also discloses cost (20 credits, Tier 2).

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 of substance plus compact metadata lines, front-loaded with what the tool returns. The duration formula earns its place as interpretive context; little waste.

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?

An output schema exists and annotations declare the safety profile, so the description only needs to say what is computed and how the reference date works, which it does. The remaining gap is routing among the many dasha-level siblings.

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 coverage is 100% and the birth-data body is richly documented in the schema. The description only adds semantics for targetDate (active MD is found at that date, default today UTC); targetTime and targetTzOffset remain unexplained, and the duration formula is interpretive rather than parameter guidance.

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 identifies the active Mahadasha at targetDate and returns the 9 Antardashas covering it. That effectively separates it from the Maha-level sibling, though it never names the maha/pratyantar/sookshma siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the level description (sub-period within MD) and the default-today note, but there is no explicit 'use this when you need X rather than pratyantar/sookshma' guidance despite a huge family of sibling dasha tools at finer 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