Skip to main content
Glama

Kundlit Vedic Astrology

by com.kundlit

Vimshottari dasha periods

get_dasha_periods
Read-onlyIdempotent

Returns the Vimshottari dasha timetable for one birth chart: the mahadasha, antardasha and pratyantardasha running right now with their end dates, the mahadasha in force at birth with its unexpired balance in years-months-days, and the full nine-mahadasha lifetime timeline with a start and end date per period. For a chart cast at the present moment no dasha has elapsed yet, so the birth mahadasha stands in and the result is flagged is_birth_fallback -- do not report it as a separately computed current period. Use this for 'which dasha am I in', 'when does my Saturn mahadasha start' and any life-period timeline question. It returns dates only -- no interpretation of what a period brings. For the planet placements those dasha lords sit in, call get_janam_kundali. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa) from the Moon's birth nakshatra; no writes, no auth. Rate limits are counted per server instance: at least 30 requests/min/IP on this endpoint, plus a shared engine budget of at least 60/min/IP across all birth-chart tools. Dates shift with birth-time accuracy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
placeNoPlace as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitudeNoLatitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
timezoneNoIANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.
longitudeNoLongitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
birth_dateYesBirth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected).
birth_timeYesBirth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart.

TDQS

A4.6/5.0
Behavior5/5

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

The description goes beyond annotations by detailing the deterministic computation method (Swiss Ephemeris, Lahiri ayanamsa from Moon's nakshatra), confirming no writes or auth, and providing specific rate limits (30 req/min/IP per endpoint, 60/min/IP shared). This fully discloses the tool's behavior and constraints, with no contradictions to the annotations.

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 description is front-loaded with the main purpose and then elaborates efficiently. While every sentence adds value, the length is slightly high, and some phrases (e.g., 'no writes, no auth') could be integrated more tightly. Overall, it is well-structured and focused.

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?

Given no output schema, the description thoroughly explains the return data (current periods with end dates, birth mahadasha with balance, full timeline with start/end, is_birth_fallback flag). It also references the sibling tool for interpretation. This covers all needed context for an agent to understand and use the tool correctly.

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%, so the baseline is 3. The description adds minimal extra meaning beyond the schema, such as noting that 'place' is preferred and geocoded, but does not significantly enhance parameter understanding. The parameter semantics are adequate but not improved beyond the schema.

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?

The description clearly states the tool returns the Vimshottari dasha timetable for one birth chart, listing specific periods (mahadasha, antardasha, pratyantardasha) and the full lifetime timeline. It explicitly distinguishes from a sibling tool (get_janam_kundali) by noting it provides only dates, not interpretations. This makes the purpose highly specific and unambiguous.

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

Usage Guidelines5/5

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

The description gives explicit use cases ('which dasha am I in', 'when does my Saturn mahadasha start'), states what the tool does not do ('no interpretation'), and directly names an alternative (get_janam_kundali). It also handles an edge case (current chart with no elapsed dasha) with clear instructions. This provides comprehensive guidance for appropriate use.

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

All Kundlit Vedic Astrology toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct astrological calculation or domain: dosha checks, birth charts, compatibility, muhurta, panchang, numerology, transits, and Jaimini layer. Even similar tools (e.g., get_panchang vs get_muhurta_timings) are explicitly differentiated in their descriptions, and cross-references tell the agent which to use for which question.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: 'get_' for data retrieval and 'check_' for yes/no dosha assessments. No camelCase or mixed conventions. The naming is predictable and readable.

Tool Count4/5

At 17 tools, the set is slightly above the ideal 15-tool ceiling, but it is well-scoped for the breadth of Vedic astrology: each tool earns its place covering a distinct sub-domain. The count feels justified rather than bloated.

Completeness5/5

The surface covers the full lifecycle of a birth chart (details, full kundli, dasha), doshas (manglik, kaal sarp, sade sati), compatibility (kundli match), event planning (muhurta, panchang, year events, eclipses), numerology (personal, mobile, name), and advanced layers (upapada, transits). No obvious gaps or dead ends.

Resources