Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Doshas: Lal Kitab Kalsarpa

astroway_vedic_doshas_lal_kitab_kalsarpa
Read-onlyIdempotent

Detect Kalsarpa dosha from Rahu-Ketu encirclement in a birth chart and get Lal Kitab remedies. Send date, time, latitude, and longitude to receive the analysis.

Instructions

Kalsarpa dosha (Rahu-Ketu encirclement) with Lal Kitab remedies.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/lal-kitab/kalsarpa] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
doshaNo
remedyNo
presentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuinely new behavioral context beyond that: it is a POST to /v1/vedic/doshas/lal-kitab/kalsarpa and costs 20 credits at Tier 2, which materially affects agent invocation decisions. It does not describe the output shape, but 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.

Conciseness5/5

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

One substantive sentence plus a compact bracketed block of group, endpoint, required fields and cost. Nothing is padded and the identifying information is front-loaded.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema lifts the burden of explaining return values, and the cost/endpoint block is present. However, for a 13-parameter tool at 23% schema coverage, the definition leaves the agent guessing about ayanamsa and house-system choices that materially change a dosha calculation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 23% across 13 parameters, and the description compensates only by restating the four required fields (date, time, latitude, longitude) already enforced by the schema. Undocumented optional parameters such as zodiacType, houseSystem, cosmogram and ayanamsaId receive no clarification of defaults or when to set them.

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?

Names a specific dosha (Kalsarpa) within a specific tradition (Lal Kitab) and even glosses it as 'Rahu-Ketu encirclement with Lal Kitab remedies.' This distinguishes it from the KP and Parashara kaal-sarp siblings that appear in the sibling list, but the description never explicitly contrasts them.

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

Usage Guidelines2/5

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

There is no statement of when to pick this over astroway_vedic_doshas_kp_kalasarpa or astroway_vedic_doshas_parashara_kaal_sarp, nor any prerequisite or exclusion. The metadata lines only list required inputs and credit cost, which is operational detail, not usage guidance.

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