Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Dashas: Kalachakra Sookshmadasha

astroway_vedic_dashas_kalachakra_sookshma
Read-onlyIdempotent

Compute Kalachakra Sookshma dasha periods with a 4-level cascade from birth details and a target date. Use it to pinpoint precise Vedic timing for any moment.

Instructions

Kalachakra Sookshmadasha: 4-level cascade.

[Group: Vedic] [Endpoint: POST /v1/vedic/dashas/kalachakra/sookshma] [Cost: 20 credits (Tier 2)]

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

Output Schema

NameRequiredDescriptionDefault
levelNo
systemNo
initialNo
periodsNo
ayanamsaNo
nakshatraNo
currentMahaNo
currentAntarNo
currentPratyantarNo
moonSiderealLongitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world. The description adds the endpoint and credit cost (20 credits, Tier 2), which is useful operational context, but it does not explain what the 4-level cascade produces, how deep the levels go, or any behavioral traits of the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and free of filler, with metadata lines that each carry some value. However, its extreme brevity leaves the core purpose under-specified rather than efficient.

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

Completeness2/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 not be explained, but for a specialized Vedic dasha tool with many sibling levels, the description does not provide enough context to know what this level means or when it should be selected. It is operationally minimal but contextually incomplete.

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 body schema thoroughly documents birth data, timezone handling, ayanamsa, and house system. The description adds no parameter meaning beyond that, so the baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name ("Kalachakra Sookshmadasha") and adds only the phrase "4-level cascade," which hints at scope without explaining what the tool computes or what a Sookshmadasha level is. It does not distinguish this tool from sibling Kalachakra dasha tools such as antar, pratyantar, maha, or prana.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to choose the sookshma level versus the other Kalachakra dasha levels, nor any prerequisites or exclusions. An agent must infer usage entirely from the tool name.

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