Skip to main content
Glama

Kundlit Vedic Astrology

by com.kundlit

Kaal Sarp dosha check

check_kaal_sarp
Read-onlyIdempotent

Returns a yes/no Kaal Sarp dosha verdict for ONE birth chart -- the condition where the seven classical grahas all fall on one side of the Rahu-Ketu axis -- plus which of the twelve named types it is (Anant, Kulik, Vasuki, Shankhpal and the rest), whether the hemming is full or partial, the houses involved, and a plain explanation of the finding. Use this for 'do I have kaal sarp dosh' questions. It is a different dosha from the Mars one (check_manglik) and from marriage-pair doshas (get_kundli_match); ask for each separately. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa); no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Needs an exact birth time -- partial hemming can flip with a few minutes' error.

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.5/5.0
Behavior5/5

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

The description discloses that the computation is read-only, deterministic, uses Swiss Ephemeris and Lahiri ayanamsa, has rate limits (30 req/min/IP per instance plus shared 60/min/IP), and warns that partial hemming can flip with time errors. These details go beyond annotations (which already indicate readOnlyHint and idempotentHint), fully informing the agent.

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 a single paragraph but contains all necessary information without redundancy. It could be slightly better structured (e.g., bullet points for rate limits), but it is efficient and clear.

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?

The description covers purpose, usage, behavior, parameter constraints, and rate limits. It lacks an explicit output schema but explains the return type. Given moderate complexity, it is quite complete, though edge cases (e.g., what happens if birth_date is invalid) are not detailed.

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 all 6 parameters. The description does not add new parameter-level detail beyond reinforcing that birth_time is required and sensitive, but it does not provide additional syntax or meaning. Baseline of 3 is appropriate.

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 identifies the tool as returning a yes/no verdict for Kaal Sarp dosha, explains the condition, and lists additional output like type and houses. It distinguishes from sibling tools by mentioning check_manglik and get_kundli_match.

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 explicitly states when to use it ('do I have kaal sarp dosh' questions) and when not to (different doshas, marriage-pair doshas). It also notes the need for an exact birth time, providing clear usage guidance.

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