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

Yogas

get_yogas

Read-onlyIdempotent

Return every yoga (planetary combination) detected in the birth chart. The result has two parts. 'summary' gives counts: 'total_yogas_found', 'total_yogas_possible', 'total_raja_yogas_found', 'total_raja_yogas_possible'. 'yoga_list' maps each detected yoga's key (e.g. nipuna_yoga, kedaara_yoga, amala_yoga) to a 4-element list: [chart it was found in (e.g. 'D1'), the yoga's display name, the condition/definition that formed it, and the effect/result it gives]. All detected yogas are included. 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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by explaining the two-part result structure, that all detected yogas are included, and that no interpretation is added, which goes beyond what the annotations express.

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 front-loaded with the primary purpose and then explains the output structure in an organized way. It is somewhat detailed, but every sentence contributes useful information such as key names, list structure, and the data-only guarantee.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining the return value, and it does so thoroughly by naming both parts, the count keys, the map structure, and example values. It also covers the all-inclusive behavior and the no-interpretation guarantee, making it complete enough for correct 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?

The input schema already provides 100% description coverage for all seven parameters, including formats, examples, and optionality. The tool description does not need to repeat parameter semantics, so the baseline of 3 is appropriate as it adds no additional parameter-level meaning.

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 clearly states the tool returns every yoga (planetary combination) detected in the birth chart, using a specific verb and resource. It also differentiates the output as data-only without interpretation, which helps distinguish it from interpretive or predictive sibling tools.

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 makes clear this is the tool for retrieving all detected yogas and describes the exact output structure and scope. It does not explicitly name alternatives or provide exclusionary conditions, but the context is specific enough that an agent can infer when to use it.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation3/5

Many tools form near-identical families—bala strengths (get_shad_bala, get_bhava_bala, get_other_bala, get_vaiseshikamsa_bala, get_vimsopaka_bala), arudhas (get_arudha_padas, get_graha_arudhas, get_chandra_arudhas, get_surya_arudhas), and transit snapshots (get_gochara, get_gochara_range, get_saturn_transit, get_muhurta). The detailed descriptions usually clarify, but an agent without deep Jyotish knowledge could easily select the wrong one, especially for vaiseshikamsa vs vimsopaka bala.

Naming Consistency4/5

The vast majority of tools use a clean get_<topic> snake_case pattern, such as get_dasha, get_muhurta, and get_yogas. The two outliers—generate_horoscope and list_divisional_charts—are still readable verb-noun names, so the inconsistency is minor.

Tool Count2/5

32 tools is above the 25+ threshold for too many. Many tools are variations on the same chart computations and could be consolidated into parameterized tools, such as a single bala strength tool with a bala_type argument. The high count will make tool selection harder for agents despite each tool covering a legitimate niche.

Completeness5/5

The surface is remarkably complete for Vedic astrology: chart generation, divisional charts, nakshatras, all major strength systems, dasha timelines, transits, muhurta, yogas, doshas, marriage matching, and specialized points are all present. There are no obvious dead ends for the core workflow of generating and analyzing a horoscope.

Resources

Need Help?