Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang)

Chandra Arudhas (from Moon)

get_chandra_arudhas

Read-onlyIdempotent

Return the chandra arudhas: the arudha sign for each of the 12 houses counted from the Moon (Chandra Lagna). Keys are 'chandra_arudha_house_1' through 'chandra_arudha_house_12'; each value is the zodiac sign of that house's arudha. Data only — no interpretation is added.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Birth date in YYYY-MM-DD format, e.g. 1985-06-15
`time`	Yes	Birth time in 24h HH:MM:SS format, e.g. 10:30:00
`place`	No	Optional birth-place name (cosmetic only).
`gender`	No	Optional. A few classical yogas are defined by gender -- Mahabhagya's rule is gender x day/night x odd/even signs. Supply it when known; when omitted those yogas are left out of the result rather than computed against an assumed gender.
`latitude`	Yes	Birth-place latitude in decimal degrees, e.g. 13.0827
`timezone`	Yes	Timezone offset from UTC in hours, e.g. 5.5 for IST
`longitude`	Yes	Birth-place longitude in decimal degrees, e.g. 80.2707

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 26, 2026

addedInput schema / properties / gender

Added value: +{
+  "description": "Optional. A few classical yogas are defined by gender -- Mahabhagya's rule is gender x day/night x odd/even signs. Supply it when known; when omitted those yogas are left out of the result rather than computed against an assumed gender.",
+  "enum": [
+    "male",
+    "female"
+  ],
+  "type": "string"
+}

First observedAug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable behavioral detail beyond those annotations by specifying the exact key naming convention, the value type, and that no interpretation is appended. This makes the tool's output behavior concrete for an agent.

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?

The description is two sentences with no filler. The core purpose and output contract are front-loaded, and the 'data only' caveat is placed at the end without bloating the definition.

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?

With no output schema present, the description compensates by fully specifying the output keys and value semantics. Given that the input contract is fully covered by the schema and the annotations declare a safe read-only operation, the definition is complete enough for reliable invocation.

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 description coverage is effectively complete, with each input parameter carrying format and example information directly in the schema. The description does not add parameter-level meaning beyond what the schema already provides, which is appropriate given the high schema coverage.

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 begins with a specific verb and resource: 'Return the chandra arudhas' and immediately defines the scope as arudha signs for 12 houses counted from the Moon. It also states the exact output keys, which distinguishes it from sibling tools like get_surya_arudhas or get_graha_arudhas without ambiguity.

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

Usage Guidelines4/5

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

The phrase 'from the Moon (Chandra Lagna)' clearly identifies the intended selection context among the arudha-related sibling tools. The explicit statement 'Data only — no interpretation is added' also tells the agent this is the raw-data variant rather than an interpretive report. However, it does not explicitly name alternatives or state when not to use this tool.

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

All Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) 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?