Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Dashas: Panchottari Sookshmadasha

astroway_vedic_dashas_panchottari_sookshma
Read-onlyIdempotent

Panchottari Sookshmadasha: the 7 sub-periods of the running period at targetDate, 4 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/sookshma] [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_sookshma"
  }
}

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
currentPratyantarNo
moonSiderealLongitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description usefully adds genuine domain behavior beyond that — the 7-way proportional split by lord-years and the non-obvious edge case where sub-periods ending before birth are dropped and the running one is truncated to start at birth. It does not mention response shape, ordering, or pagination, though 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?

The core definition is one dense but well-ordered sentence: what it returns, at what depth, and how periods are divided. The birth-mahadasha caveat follows as a second short sentence, and the Group/Endpoint/Cost lines are compact boilerplate. No filler, and the most important fact (7 sub-periods at targetDate) is front-loaded.

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 3-parameter, read-only Vedic calculation with an output schema and full schema coverage, the definition supplies the calculation semantics and the one genuinely surprising edge case. Cost tier and endpoint are stated. The remaining gap is that it does not convey how the four nesting levels are represented or which sibling to pick for other depths.

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?

With schema coverage at 100% the schema does most of the work, and the description adds one genuinely useful piece of semantics: `targetDate` selects the running period being subdivided. It says nothing about targetTime/targetTzOffset (which matter for picking the running period at a moment) or about the compact-mode `fields`/`precision` parameters.

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 a specific technique and level (Panchottari Sookshmadasha), states the output is the 7 sub-periods of the running period at `targetDate` at depth 4, and explains the proportional split rule. It is precise about what is computed, but it never contrasts itself with the adjacent panchottari_antar, _pratyantar, _prana, or _maha siblings, so an agent must infer the level ordering from the naming convention.

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: an agent can deduce this is the sookshma-level query for the Panchottari system, but there is no explicit 'use this when you need X rather than Y' statement and no guidance on choosing between the five panchottari depth tools. The birth-mahadasha note is a rule of the calculation rather than selection guidance.

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