Skip to main content
Glama

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

by com.jagannathahora

Other Bala

get_other_bala
Read-onlyIdempotent

Return the additional planetary strength measures for the seven planets (Sun..Saturn). Contains 'harsha_bala' (joy/positional strength), 'pancha_vargeeya_bala' (five-source compound strength), 'dwadhasa_vargeeya_bala' (twelve-source strength), 'ishta_phala' (benefic result, 0-60) and 'kashta_phala' (malefic result, 60 - ishta). Each is a map of planet name to its value. Data only — no interpretation is added.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format, e.g. 1985-06-15
timeYesBirth time in 24h HH:MM:SS format, e.g. 10:30:00
placeNoOptional birth-place name (cosmetic only).
genderNoOptional. 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.
latitudeYesBirth-place latitude in decimal degrees, e.g. 13.0827
timezoneYesTimezone offset from UTC in hours, e.g. 5.5 for IST
longitudeYesBirth-place longitude in decimal degrees, e.g. 80.2707

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations by revealing that each result is a map keyed by planet name, that ishta_phala ranges 0-60, that kashta_phala is computed as 60 minus ishta, and that no interpretation is added.

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 compact and front-loaded with the core purpose, followed by a well-organized enumeration of the returned measures. Each field explanation earns its place, and there is no filler or repetition of schema details.

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?

Even without an output schema, the description fully explains what the return value contains: the seven planets, each measure's meaning, the planetary-keyed map structure, and the numeric ranges for the two phala measures. It also sets expectations that this is raw data with no interpretive layer, which is sufficient for an agent to invoke the tool correctly.

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 input schema already documents all parameters including formats, examples, and optionality. The description does not add parameter-level semantics, but per the baseline rule, high schema coverage makes this acceptable.

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?

States a specific verb ('Return') and an unambiguous resource: the additional planetary strength measures for the seven planets. It enumerates the exact measures contained, making it easy to distinguish from sibling bala tools like get_shad_bala or get_vaiseshikamsa_bala even though it does not name them.

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?

The description implies usage by listing the specific measures returned, but it does not explicitly say when to choose this tool over the other bala-related siblings. The phrase 'additional planetary strength measures' gives some contextual cue, but there is no direct alternative comparison or exclusion.

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) toolsInspect
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