Skip to main content
Glama

Cosmic Chemistry

Raj yogas in a birth chart

raj_yoga
Read-onlyIdempotent

Use this when someone asks whether they have raj yoga (raja yoga) or another yoga in their kundli or birth chart, how strong a yoga is, or when it will activate ("do I have raj yoga", "raj yoga calculator", "Gaja Kesari yoga in my chart", "vipreet raj yoga", "neecha bhanga raja yoga", "Malavya yoga", "when will my raj yoga give results"). Returns each classical yoga the chart holds: raja yogas from the lords of the angles and trines, Maha Raja yoga, the yogakaraka, Gaja Kesari, the five Mahapurusha yogas (Ruchaka, Bhadra, Hamsa, Malavya, Sasa), Lakshmi, Neecha Bhanga and Vipreet (Harsha, Sarala, Vimala), plus Budhaditya marked as a modern yoga. For each: how it forms in this chart, its strength on the classical scale (full, half or a quarter, from each planet’s shadbala against the strength the classical texts ask), whether its planets’ period is running now or the next dated window, and how common it is in our sample of 20,000 charts. Needs birth date, time and town; future dates to 2100 work too.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "raj_yoga"
  }
}

Input Schema

NameRequiredDescriptionDefault
birth_dateYesDate of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_timeYesLocal clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_placeYesTown or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: the exact output inventory, the strength grading method (shadbala measured against what classical texts ask, reported as full/half/quarter), the dasha timing report, a rarity statistic from a 20,000-chart sample, and the supported date range up to 2100.

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?

Front-loaded with the trigger condition, then output inventory, then input requirements — a logical order with no filler sentences. The parenthetical list of seven verbatim user phrasings is slightly padded, but each one targets a distinct yoga variant and aids routing, so the cost is small.

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?

With no output schema, the description carries the full burden of explaining returns, and it does so precisely: per-yoga formation, strength grade, current-or-next dasha window, and population rarity. Inputs, date limits and scope are all covered, leaving nothing an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the three inputs are already documented, making 3 the baseline. The description adds two things the schema does not: that the tool needs all of birth date, time and town, and that future dates to 2100 are supported — a real usage boundary an agent would otherwise not know.

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 and resource ('Returns each classical yoga the chart holds') and then enumerates exactly which yogas: raja yogas from lords of angles and trines, Maha Raja, yogakaraka, Gaja Kesari, the five Mahapurusha yogas, Lakshmi, Neecha Bhanga, Vipreet, Budhaditya. That enumeration, plus the sample user phrasings, makes it unmistakable against generic siblings like vedic_birth_chart or divisional_chart.

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?

Opens with an explicit trigger condition — 'Use this when someone asks whether they have raj yoga ... how strong a yoga is, or when it will activate' — backed by five quoted example queries that map real user phrasing onto the tool. It stops short of naming a sibling to use instead for non-yoga chart questions, so there is no explicit when-not clause.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources