AstroWay Vedic astrology

Dashas: Panchottari Pranadasha

astroway_vedic_dashas_panchottari_prana

Read-onlyIdempotent

Panchottari Pranadasha: the 7 sub-periods of the running period at targetDate, 5 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/prana] [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_panchottari_prana"
  }
}

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
`currentSookshma`	No
`currentPratyantar`	No
`moonSiderealLongitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description is free to add computation semantics — proportional splitting by the lords' years, the notional start of the birth mahadasha, and how sub-periods ending before birth are dropped. The credit cost (20 credits, Tier 2) is also disclosed, which annotations cannot express.

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?

Front-loaded with the technique name and the returned structure, followed by the one genuinely non-obvious caveat about the birth mahadasha. Two dense sentences plus terse metadata lines; nothing is padding, though the second sentence is dense enough to need a second read.

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 values need no explanation, and the birth data is fully specified in the schema. However, `targetDate` is optional in the schema and the description never states the default (presumably now), and no guidance links this level to its four panchottari siblings — a real gap for an agent choosing among 400+ tools.

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 nested birth-data object is thoroughly documented, so the schema carries the load. The description adds only the meaning of `targetDate` as the moment whose running period is decomposed; it says nothing about `targetTime`, `targetTzOffset`, or what happens when `targetDate` is omitted (it is not required).

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 exact technique (Panchottari Pranadasha), states that it returns the 7 sub-periods of the running period at `targetDate`, and specifies depth (5 levels). That is enough to tell it apart from the sibling panchottari_maha/antar/pratyantar/sookshma tools by level, though it never explicitly says so.

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?

Usage is only implied through the dasha-level naming and the `targetDate` reference. There is no explicit statement of when to reach for prana versus the coarser panchottari levels, and no prerequisites or exclusions are given.

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?