Skip to main content
Glama
astroway

astroway-mcp

Official

Dashas — Shatabdika Antardasha

vedic_dashas_shatabdika_antar
Read-onlyIdempotent

Compute the seven Shatabdika Antardasha sub-periods of the running Mahadasha for a specific target date using recursive proportional splits.

Instructions

Shatabdika Antardasha — 7 sub-periods of the running MD at targetDate. Recursive proportional split (parent_years × sub_planet_period / 100).

[Group: Vedic]

Example request body: {"date":"1947-08-15","time":"02:00:00","timezoneOffset":5.5,"latitude":27.49,"longitude":77.67,"targetDate":"2026-05-06"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
Behavior4/5

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

Annotations already indicate readOnly=true. Description adds the recursive proportional split formula, providing useful behavioral context without contradiction.

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?

Description is concise, front-loads purpose, and includes an example. Slightly more structure could improve readability.

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?

No output schema, and description does not specify what the response contains (e.g., list of sub-periods with dates). Lacks essential detail for a complex dasha tool.

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 baseline is 3. Description mentions targetDate and calculation but does not explain targetTime/targetTzOffset or output format.

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?

Description clearly states it computes the 7 sub-periods (antardasha) of the running Mahadasha at a target date, differentiating it from sibling tools like maha, prana, etc.

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?

No guidance on when to use this tool relative to alternatives such as vimshottari or other dasha systems; lacks context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server