Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Dashas: Panchottari Pratyantardasha

astroway_vedic_dashas_panchottari_pratyantar
Read-onlyIdempotent

Panchottari Pratyantardasha: the 7 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/panchottari/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_panchottari_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.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
levelNo
systemNo
initialNo
periodsNo
ayanamsaNo
nakshatraNo
currentMahaNo
currentAntarNo
moonSiderealLongitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, and the description goes further by explaining the proportional split rule (by the lords' years from the period's own lord) and the birth-mahadasha edge case where pre-birth sub-periods are dropped and the running one begins at birth. It also surfaces the cost tier, which is not in the schema. What it omits is the response shape and ordering of the 7 periods.

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 led by the resource name, followed by a compact Group/Endpoint/Cost block. Every clause carries information, though the trailing bracket metadata is boilerplate that adds length rather than selection signal.

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?

For a computational dasha endpoint with full schema coverage and an output schema, the description supplies exactly the missing pieces: the split rule, the depth, the referring date, and the birth-boundary special case. An agent can call it correctly without further documentation.

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 the schema already documents body, fields and precision. The description contributes meaning only for targetDate, which the schema leaves undocumented by defining it as the moment whose running period is decomposed. It says nothing about targetTime, targetTzOffset, fields or precision beyond what the schema provides, so the baseline 3 applies.

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 resource (Panchottari Pratyantardasha) and what it returns: the 7 sub-periods of the running period at targetDate, three levels deep. It is clear about its own output, but it never positions itself against the many sibling dasha tools (panchottari_antar, panchottari_prana, panchottari_sookshma), so the agent must infer that 'pratyantar' is a specific depth tier.

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: the mention of targetDate signals you call it for a specific moment, and the three-levels-deep phrasing hints at its position in the dasha hierarchy. There is no explicit when-to-use or when-not-to-use guidance and no sibling alternative is named, despite the tool sitting in a dense cluster of near-identical dasha endpoints.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources