AstroWay Astrology API (full catalogue)

Dashas: Dwadashottari Mahadasha

astroway_vedic_dashas_dwadashottari_maha

Read-onlyIdempotent

Dwadashottari Dasha, 112-year nakshatra cycle of 8 lords. BPHS 46.27-28: the stars from the birth star to Revati, divided by 8, give the first lord; Sun 7, Jupiter 9, Ketu 11, Mercury 13, Rahu 15, Mars 17, Saturn 19, Moon 21 years (Venus left out). Given for a lagna in a Venus navamsa: initial.applicable reports it, the periods are computed either way.

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

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": {
      "body": "<body>"
    },
    "name": "astroway_vedic_dashas_dwadashottari_maha"
  }
}

Input Schema

Name	Required	Description
`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.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so safety needs no restating. The description does add real behavioral context: that `initial.applicable` flags whether the chart qualifies for a Venus navamsa lagna but periods are computed regardless, plus the 20-credit Tier 2 cost. It says nothing about period boundaries, the time span returned, or how targetDate affects output.

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?

The first sentence states the cycle and lord count, which is a good lead. The BPHS citation and the per-planet year list (Sun 7 ... Moon 21) are scholarly background rather than invocation guidance, and they occupy most of the text while operational details are absent.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required, and the annotations cover the safety profile. However, for a 3-parameter tool with target-date fields and four finer-grained sibling tools, the description leaves the agent without guidance on level selection or on what targetDate does.

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 nested body description already covers date/time/latitude/longitude, timezone handling, and field rejection rules. The description adds no meaning for targetDate/targetTime/targetTzOffset, which are the parameters most in need of explanation for a dasha tool, so it stays at baseline.

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 the specific dasha (Dwadashottari, 112-year cycle of 8 lords) and states that the periods are computed from the birth star, so an agent knows what resource is produced. It never explicitly contrasts itself with the sibling dwadashottari_antar/pratyantar/sookshma/prana tools, so the maha-level scope is implied by the title rather than spelled out.

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 statement of when to pick this over vimshottari_maha or any other dasha system, and no mention of the subordinate dwadashottari tools for finer levels. The only conditional guidance is the Venus-navamsa applicability note, which concerns validity of results rather than tool selection.

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

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?