Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Dashas: Vimshottari Pratyantardasha

astroway_vedic_dashas_vimshottari_pratyantar
Read-onlyIdempotent

Computes Vimshottari Pratyantardasha sub-sub-periods for the current Mahadasha and Antardasha from birth data, returning the 9 PDs (or fewer if birth cuts them short).

Instructions

Pratyantardasha (sub-sub-period) within the running Antardasha. 3-level cascade: find current MD → AD → return the PDs of that AD (9, or fewer inside the birth periods, where the ones that ended before birth are left out).

[Group: Vedic] [Endpoint: POST /v1/vedic/dashas/vimshottari/pratyantar] [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_vimshottari_pratyantar"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesBirth 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.

Output Schema

NameRequiredDescriptionDefault
levelNo
systemNo
initialNo
periodsNo
ayanamsaNo
nakshatraNo
currentMahaNo
currentAntarNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.1
    • changedInput schema / properties / body / allOf
      Previous value: -[
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "description": "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.",
      -    "properties": {
      -      "ayanamsa": {
      -        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      -        "enum": [
      -          "fagan-bradley",
      -          "lahiri",
      -          "de-luce",
      -          "raman",
      -          "krishnamurti",
      -          "kp",
      -          "yukteshwar",
      -          "jn-bhasin",
      -          "true-citra",
      -          "djwhal-khul"
      -        ],
      -        "type": "string"
      -      },
      -      "ayanamsaId": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "city": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "cosmogram": {
      -        "type": "boolean"
      -      },
      -      "date": {
      -        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -        "type": "string"
      -      },
      -      "houseSystem": {
      -        "default": "P",
      -        "enum": [
      -          "P",
      -          "K",
      -          "R",
      -          "C",
      -          "E",
      -          "W",
      -          "B",
      -          "M",
      -          "O",
      -          "A",
      -          "T",
      -          "V",
      -          "D",
      -          "F",
      -          "G",
      -          "H",
      -          "I",
      -          "i",
      -          "L",
      -          "N",
      -          "Q",
      -          "S",
      -          "U",
      -          "X",
      -          "Y"
      -        ],
      -        "type": "string"
      -      },
      -      "latitude": {
      -        "maximum": 90,
      -        "minimum": -90,
      -        "type": "number"
      -      },
      -      "longitude": {
      -        "maximum": 180,
      -        "minimum": -180,
      -        "type": "number"
      -      },
      -      "name": {
      -        "default": "",
      -        "type": "string"
      -      },
      -      "time": {
      -        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -        "type": "string"
      -      },
      -      "timezone": {
      -        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      -        "type": "string"
      -      },
      -      "timezoneOffset": {
      -        "anyOf": [
      -          {
      -            "maximum": 14,
      -            "minimum": -14,
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": 0,
      -        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      -      },
      -      "zodiacType": {
      -        "enum": [
      -          "tropical",
      -          "sidereal"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "date",
      -      "time",
      -      "latitude",
      -      "longitude"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {},
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "properties": {
      -      "targetDate": {
      -        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      -        "type": "string"
      -      },
      -      "targetTime": {
      -        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      -        "type": "string"
      -      },
      -      "targetTzOffset": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "description": "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.",
      +    "properties": {
      +      "ayanamsa": {
      +        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
      +        "enum": [
      +          "fagan-bradley",
      +          "lahiri",
      +          "de-luce",
      +          "raman",
      +          "krishnamurti",
      +          "kp",
      +          "yukteshwar",
      +          "jn-bhasin",
      +          "true-citra",
      +          "djwhal-khul"
      +        ],
      +        "type": "string"
      +      },
      +      "ayanamsaId": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "city": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "cosmogram": {
      +        "type": "boolean"
      +      },
      +      "date": {
      +        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +        "type": "string"
      +      },
      +      "houseSystem": {
      +        "default": "P",
      +        "enum": [
      +          "P",
      +          "K",
      +          "R",
      +          "C",
      +          "E",
      +          "W",
      +          "B",
      +          "M",
      +          "O",
      +          "A",
      +          "T",
      +          "V",
      +          "D",
      +          "F",
      +          "G",
      +          "H",
      +          "I",
      +          "i",
      +          "L",
      +          "N",
      +          "Q",
      +          "S",
      +          "U",
      +          "X",
      +          "Y"
      +        ],
      +        "type": "string"
      +      },
      +      "latitude": {
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      "longitude": {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      },
      +      "name": {
      +        "default": "",
      +        "type": "string"
      +      },
      +      "time": {
      +        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +        "type": "string"
      +      },
      +      "timezone": {
      +        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
      +        "type": "string"
      +      },
      +      "timezoneOffset": {
      +        "anyOf": [
      +          {
      +            "maximum": 14,
      +            "minimum": -14,
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": 0,
      +        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
      +      },
      +      "zodiacType": {
      +        "enum": [
      +          "tropical",
      +          "sidereal"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "date",
      +      "time",
      +      "latitude",
      +      "longitude"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "properties": {
      +      "targetDate": {
      +        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +        "type": "string"
      +      },
      +      "targetTime": {
      +        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
      +        "type": "string"
      +      },
      +      "targetTzOffset": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / body / description
      Previous value: -"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."New value: +"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."
  2. Addedv1.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description only needs to add what they don't. It does add two things an agent cannot get elsewhere: the expected result cardinality (9 PDs, fewer when some ended before birth) and the cost (20 credits, Tier 2), plus the endpoint. It does not discuss error modes or precision/edge cases around the birth boundary beyond the brief parenthetical.

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?

The core sentence is front-loaded and dense with useful information, and the bracketed group/endpoint/cost line is scannable metadata. Minor waste in restating the hierarchy in two ways, but nothing misleading or padded.

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

Completeness5/5

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

Output schema is present, so return-value structure needn't be explained; annotations carry the safety profile; the schema carries parameter detail. What remains — which hierarchy level this returns, how many items, and what it costs — is exactly what the description supplies.

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 single body parameter is documented in exceptional depth (timezone handling, houseSystem letters, rejected field aliases). The description adds no parameter-level meaning — targetDate, targetTime and targetTzOffset are never mentioned, so the agent must read the schema to learn that a target moment drives the 'running' period selection.

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?

States a precise verb+resource — returns the Pratyantardasha (third-level) periods inside the running Antardasha — and spells out the MD → AD → PD cascade, which unambiguously separates it from the maha (level 1), antar (level 2) and prana (level 4) siblings.

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?

The cascade explanation implies when this depth level is appropriate, but there is no explicit 'use this instead of antar/prana when…' routing and no stated prerequisites (e.g. that the birth data must already produce a running dasha). Usage is inferable rather than stated.

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

Deploy Server

Other Tools