Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Doshas: Kaal Sarp

astroway_vedic_doshas_parashara_kaal_sarp
Read-onlyIdempotent

Detects Kaal Sarp Dosha by checking if all seven classical planets lie on one side of the Rahu-Ketu axis, returns one of 12 sub-types by Rahu's house position, and flags partial doshas.

Instructions

Kaal Sarp Dosha: all 7 classical grahas on one side of the Rahu-Ketu axis. Returns 12 sub-types by Rahu house position (Anant=1H, Kulik=2H, Vasuki=3H, Shankhpal=4H, Padma=5H, Mahapadma=6H, Takshak=7H, Karkotak=8H, Shankhachud=9H, Ghatak=10H, Vishdhar=11H, Sheshnag=12H). Also partial: true flag when 6 of 7 grahas on one side.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/parashara/kaal-sarp] [Required: date, time, latitude, longitude] [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": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_doshas_parashara_kaal_sarp"
  }
}

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
schoolNo
detailsNo
partialNo
presentNo
subTypeNo
severityNo
affectedHousesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine domain semantics beyond that: what constitutes a full dosha versus a partial one, and how the 12 named sub-types map to Rahu's house. It says nothing about failure modes (e.g. what happens with missing latitude) or the credit cost.

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?

Two sentences, front-loaded with the definition and then the return shape. The twelve-name enumeration is long but earns its place as an output legend an agent cannot get elsewhere, and the partial-flag caveat is correctly appended last.

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?

An output schema exists, so return values need not be explained, and the domain definition is solid. But for a 13-parameter sidereal calculation with thin schema coverage, the description should at least flag that ayanamsa and timezone choices affect the outcome; an agent has no textual basis for setting them here.

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?

13 parameters at 23% schema description coverage, and the description mentions none of them. The ayanamsa, timezone and timezoneOffset fields carry schema text, but houseSystem's bare enum letters, zodiacType, cosmogram, ayanamsaId, city and name are undocumented in both places, and the description does not compensate or even note that sidereal settings materially change the dosha result.

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?

States the specific calculation: all 7 classical grahas on one side of the Rahu-Ketu axis, plus the 12 Rahu-house sub-types and the partial-flag threshold. That is a precise verb+resource+criteria statement. It does not, however, distinguish itself in-text from the neighbouring dosha tools (kp_kalasarpa, lal_kitab_kalsarpa, parashara_full), which the endpoint namespace only implies.

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?

The text defines the condition being tested but never says when an agent should pick this tool over astroway_vedic_doshas_kp_kalasarpa or astroway_vedic_doshas_lal_kitab_kalsarpa, nor any prerequisites or exclusions. Usage is only inferable from the school name embedded in the endpoint.

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