Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Doshas: Guru-Chandal

astroway_vedic_doshas_parashara_guru_chandal
Read-onlyIdempotent

Calculate Guru-Chandal Dosha presence by checking Jupiter-Rahu or Jupiter-Ketu conjunctions using your birth date, time, and coordinates.

Instructions

Guru-Chandal Dosha: Jupiter + Rahu or Jupiter + Ketu conjunct. Wisdom-confusion affliction.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/parashara/guru-chandal] [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_guru_chandal"
  }
}

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
presentNo
severityNo
lagnaSignNo
affectedHousesNo
contributingPlanetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive closed-world call, so the safety profile is covered. The description adds genuinely useful context the annotations lack: a 20-credit Tier 2 cost and the exact required input set. It says nothing about computation depth, output structure or failure behavior, though 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.

Conciseness4/5

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

Two content sentences plus bracketed metadata lines, with the dosha definition front-loaded and machine-readable tags after it. Efficient overall, though 'Guru-Chandal Dosha' partially restates the title and name.

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 and annotations exist, so return values and safety need not be spelled out. However, for a 13-parameter chart computation the description omits how the sidereal/house-system options affect the dosha determination and gives no scope statement about the result, leaving meaningful gaps.

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, so the description should compensate, but it only repeats the four required fields already marked required in the schema. Undocumented parameters such as houseSystem, zodiacType, cosmogram, ayanamsaId and name/city receive no explanation anywhere.

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?

The description defines the specific affliction being computed (Jupiter conjunct Rahu or Ketu) and names the Parashara dosha family, so an agent can distinguish it from sibling dosha tools such as mangal, pitru or kaal_sarp. It never states the verb ('detects/analyzes this dosha in a birth chart'), leaving the action implicit, but the resource is unambiguous.

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 guidance on when to select this narrow single-dosha endpoint versus astroway_vedic_doshas_parashara_full or the other parashara dosha tools, and no prerequisites or exclusions are given. The '[Required: ...]' line only restates inputs, not usage conditions.

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