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

Transit Snapshot (Gochara)

get_gochara

Read-onlyIdempotent

Planetary transit (Gochara) snapshot for a given date vs the natal chart. Returns that day's panchanga (vara, tithi+rikta, nakshatra, yoga, karana, paksha), muhurta windows (sunrise/sunset, Abhijit plus a clean Abhijit with Rahu/Gulika/Yamaganda overlap removed, and the avoid windows), all 9 planets (sign, degree, nakshatra/pada, retrograde, combust, house from Moon and Lagna, Ashtakavarga bindus, Gochara-phala favourable/Vedha), and the native's Tara Bala (Moon/Sun/Lagna), Chandra Bala and Sade Sati. Also returns the transit moment's D-1 (Rasi) and D-9 (Navamsa) charts under 'transit_charts' — each planet plus the Ascendant with sign and longitude. Rahu/Ketu use the Mean node by default; pass node_type='true' for True nodes. Data only — no verdict.

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.
`include`	No	Enrichment sections: 'ashtakavarga', 'gochara_phala', 'transit_charts' (default all three). Pass [] for lean.
`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
`node_type`	No	Rahu/Ketu node: 'mean' (default) or 'true'.
`event_place`	No	Event place name (optional; defaults to birth place)
`target_date`	Yes	Target date YYYY-MM-DD
`target_time`	No	Target time HH:MM:SS (default local noon)
`event_latitude`	No	Event latitude (optional)
`event_timezone`	No	Event timezone offset from UTC (optional)
`event_elevation`	No	Event elevation in metres (optional)
`event_longitude`	No	Event longitude (optional)

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.1/5.0

Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive, so the bar is lower. The description adds genuinely useful behavioral details: Rahu/Ketu default to Mean node, a clean Abhijit window excluding Rahu/Gulika/Yamaganda overlap, the gender-sensitive yoga behavior, and the 'Data only — no verdict' boundary. These are beyond what annotations state.

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?

The description is compact for the amount of content it covers. It front-loads the primary purpose (transit snapshot for a given date vs natal chart), then lists return sections and key behaviors. It could be a touch shorter, but every clause adds information about scope, defaults, or exclusions.

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?

For a complex tool with 16 parameters and no output schema, the description covers the main return categories, the default node behavior, and the no-verdict boundary. It doesn't spell out every default (target_time default, event_place default), but the schema already documents those defaults, so the description needn't repeat them. The main gap is not describing the shape of the transit_charts output, but the schema and the description together are adequate.

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 100%, so the schema fully documents all 16 parameters. The description restates a few schema concepts (node_type default, gender optionality) but doesn't add much new meaning. It correctly orients the agent to the birth vs target_date distinction, but the schema already does that. Baseline 3 is appropriate.

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 is specific: it names the resource (planetary transit snapshot vs natal chart), the date (target date vs birth), and enumerates concrete content: panchanga, muhurta windows, 9 planets, Tara Bala, D-1/D-9 charts, node behavior. It clearly distinguishes itself from get_gochara_range and other astrological siblings by focusing on a single target date.

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 description clearly states what data is returned and that no verdict is provided ('Data only — no verdict'), which tells the agent when not to use it for interpretive judgment. It also mentions node_type='true' for True nodes, implying the default Mean behavior is the common case. It doesn't explicitly name alternatives, but the richness of the content and the date-vs-range distinction vs get_gochara_range is implicit.

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?