AstroWay Vedic astrology

Yogas: Chandra (Sunapha, Anapha, Durudhara, Kemadruma)

astroway_vedic_yogas_parashara_chandra

Read-onlyIdempotent

Yogas counted from the Moon, BPHS ch. 37: Sunapha (a planet other than the Sun in the 2nd from the Moon), Anapha (12th), Durudhara (both), st. 7; Kemadruma (nothing beside the Moon and nothing but the Moon in a kendra from the lagna, each condition returned), st. 11-12; benefics in the upachayas from the Moon, st. 6. Rahu and Ketu are not counted. The yoga and the planets that form it; no result text.

[Group: Vedic] [Endpoint: POST /v1/vedic/yogas/parashara/chandra] [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_yogas_parashara_chandra"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	IANA 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.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	Hours 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

Name	Required	Description	Default
`yoga`	No
`anapha`	No
`school`	No
`sources`	No
`sunapha`	No
`moonSign`	No
`durudhara`	No
`kemadruma`	No
`lagnaSign`	No
`upachayaBenefics`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: it discloses that no interpretive result text is returned, that each Kemadruma condition is returned separately, and that Rahu/Ketu are excluded from counting. It does not mention the 20-credit cost or that the result depends on the sidereal/ayanamsa setting, both of which affect invocation.

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?

Dense but well front-loaded: the governing rule ('counted from the Moon') comes first, then each yoga with its definition and sutra reference, then the exclusion and output note. Sutra shorthand ('st. 7', 'st. 11-12') is terse but readable for the intended audience. No filler sentences.

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 do not need explaining, and the description still usefully caps expectations with 'no result text.' For a 15-parameter tool with only a third of parameters documented in the schema, however, the description leaves the invocation surface (ayanamsa choice, timezone handling, required coordinates) entirely to the schema, which does not fully cover it.

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 33% across 15 parameters, so the description would need to compensate and it says nothing about any parameter. It never states that date/time/latitude/longitude are required, never indicates that ayanamsa or zodiacType affects which sidereal positions the yogas are computed from, and never touches the compact-mode fields/precision options.

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 states precisely what is computed: Sunapha, Anapha, Durudhara, Kemadruma and benefics in upachayas from the Moon, with BPHS chapter and sutra citations and an explicit exclusion rule (Rahu/Ketu not counted). The scope is unambiguous and the yoga names themselves separate it from the Surya/Gajakesari/Adhi siblings. It stops short of naming or routing away from those sibling tools, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the domain: an agent infers it is for Moon-based Parashara yogas on a birth chart. There is no explicit statement of when to pick this over astroway_vedic_yogas_parashara_full or astroway_vedic_doshas_kp_kemadruma, and no note that natal date/time/place are required to compute the yoga at all.

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

All AstroWay Vedic astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?