astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Dashas: Yogini Antardasha

astroway_vedic_dashas_yogini_antar

Read-onlyIdempotent

Calculates the eight Yogini Antardasha sub-periods within the running Mahadasha for a given target date and natal chart, returning Vedic dasha timing.

Instructions

Yogini Antardasha: 8 sub-periods of the running MD at targetDate (default today UTC). Sub-period of yogini Q within MD of P: years = (P.years × Q.years) / 36.

[Group: Vedic] [Endpoint: POST /v1/vedic/dashas/yogini/antar] [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 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

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's job is lighter. It adds real value beyond the annotations by disclosing the cost (20 credits, Tier 2), the endpoint, and the default targetDate of today UTC — none of which appear in the structured fields.

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 front-loaded sentences plus compact metadata lines for group, endpoint and cost. Every element earns its place; nothing is padded.

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 an output schema and full annotation set, the description only needs to cover scope, defaults and cost, which it does. The one remaining gap is explicit differentiation from the other Yogini dasha levels, which matters given how many sibling dashas exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description adds meaning not present in the schema: targetDate has no description in the schema, and the text supplies its 'default today UTC' behavior. The P/Q formula also clarifies the period math, though the underlying body fields are already well documented.

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 the specific operation: returns the 8 Yogini antardasha sub-periods of the running mahadasha at targetDate. The level (antar, second-order) is clear from the text and title, but it never explicitly contrasts itself with sibling levels such as yogini_maha, pratyantar, sookshma or prana.

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?

Implicit guidance comes from '8 sub-periods of the running MD at targetDate (default today UTC)', which tells the agent this is the second-level breakdown. However, no explicit when-to-use/when-not or 'use X instead for deeper levels' routing is offered, and there are four close sibling Yogini dasha tools.

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

Deploy Server