astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Dashas: Panchottari Pratyantardasha

astroway_vedic_dashas_panchottari_pratyantar

Read-onlyIdempotent

Computes Panchottari Pratyantardasha sub-periods three levels deep for a target date, showing which planetary sub-period is running within the birth mahadasha, split by each lord's years.

Instructions

Panchottari Pratyantardasha: the 7 sub-periods of the running period at targetDate, 3 levels deep, split in proportion to the lords' years from the period's own lord. Inside the birth mahadasha the split follows the full period from its notional start: sub-periods that ended before birth are left out and the running one starts at birth.

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

Input Schema

Name	Required	Description	Default
`body`	Yes	Birth 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 house-system 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

Name	Required	Description	Default
`level`	No
`system`	No
`initial`	No
`periods`	No
`ayanamsa`	No
`nakshatra`	No
`currentMaha`	No
`currentAntar`	No
`moonSiderealLongitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.1Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a safe, read-only, idempotent query. The description adds meaningful domain behavior: proportional splitting by lord years, 3-level depth, and the special handling of sub-periods before birth inside the birth mahadasha, plus endpoint and 20-credit cost. It stops short of auth/rate details, but adds substantial context beyond 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?

Two tightly written sentences front-load the definition and follow with the birth-mahadasha exception; the bracketed endpoint/cost metadata is separate and easy to scan. No wasted 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?

With a full input schema, an output schema, and safety annotations, the description supplies the calculation semantics needed to interpret the result. The main remaining gap is guidance on selecting this depth versus sibling dashas, which keeps it just short of fully 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 coverage is 100%, so the schema carries parameter documentation. The description adds semantic context for `targetDate` (selects the running period) and the birth-data edge case, but does not explain individual input fields beyond 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?

The description names a specific dasha level and states exactly what is returned: the 7 sub-periods of the running period at `targetDate`, 3 levels deep. It is clear what the tool computes, though it does not explicitly compare itself with the maha/antar/prana/sookshma siblings.

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?

It implies when the tool applies by specifying the pratyantar level and `targetDate` selection, but it gives no explicit when-to-use guidance, no exclusions, and no named alternative for different dasha depths. An agent must know the dasha hierarchy to choose this over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server