AstroWay Vedic astrology

Dashas: Dwadashottari Pratyantardasha

astroway_vd_dwadashottari_pratyantar

Read-onlyIdempotent

Dwadashottari Pratyantardasha: the 8 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/dwadashottari/pratyantar] [Cost: 20 credits (Tier 2)]

(Cursor-friendly alias for astroway_vedic_dashas_dwadashottari_pratyantar.)

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_vd_dwadashottari_pratyantar"
  }
}

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
`currentMaha`	No
`currentAntar`	No
`moonSiderealLongitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description is free to spend its words on real behavior — and it does: fixed count of 8 sub-periods, proportional splitting by each lord's year-count from the period's own lord, and the non-obvious rule that inside the birth mahadasha the split runs from the notional start with pre-birth sub-periods dropped and the running one truncated at birth. It also discloses group, endpoint and the 20-credit Tier 2 cost, which no annotation carries. It does not describe the response payload, but an output schema exists.

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 dense sentences lead with the definition and the birth-boundary edge case, then a compact metadata block for group, endpoint, cost and the alias relationship. Nothing is padded, though the alias parenthetical is the least load-bearing line.

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?

For a computation-heavy Vedic dasha tool the description supplies the algorithmic contract the agent cannot get from the schema, and the output schema plus annotations cover return shape and safety. The remaining gap is navigational — nothing tells the agent when this level is the right one to call versus the antar or sookshma variants.

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 description coverage is 100% and the body schema is unusually rich (timezone, ayanamsa, houseSystem caveats), so the schema does the heavy lifting. The description adds only one parameter-level fact beyond it: that `targetDate` selects the running period being subdivided. It says nothing about how `targetTime`/`targetTzOffset`, `fields`, or `precision` interact with the result.

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 states a specific verb-plus-resource: it returns the 8 sub-periods of the running Dwadashottari period at `targetDate`, at 3 levels deep. Saying '3 levels deep' implicitly locates this against the antar/prana siblings, but it never explicitly names those levels or the sibling tools, so the agent must infer where pratyantar sits in the maha > antar > pratyantar > sookshma > prana stack.

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 when-to-use guidance: no statement that the agent should pick this only after knowing the running mahadasha, no comparison with `astroway_vedic_dashas_dwadashottari_antar` or `_sookshma`, and no note that the only named alternative (`astroway_vedic_dashas_dwadashottari_pratyantar`) is an identical alias rather than a different tool. Usage must be inferred entirely from the calculation semantics.

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

All AstroWay Vedic astrology 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?