Skip to main content
Glama

Supastro

Find the yogas in a birth chart

find_chart_yogas
Read-onlyIdempotent

Finds the classical yogas (planetary combinations) formed in a birth chart, such as Gajakesari, Budha-Aditya, Raja, Dhana and Pancha Mahapurusha yogas. For each one it names the planets and houses that form it, the classical text and verse the rule comes from, the result that text gives, one status (Active now, Between periods, Yet to begin, Completed, Lifelong or Dormant) with when it last ran and next runs, and every Mahadasha and Antardasha in which it was active in the past, is active now or will be active, each with start date, end date and length. It opens with a count of the yogas in each status. Use it when someone asks which yogas they have, whether a named yoga is in their chart, or when a yoga was or becomes active. Also lists yogas that are formed but dormant, with the reason and no dates.

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": "find_chart_yogas"
  }
}

Input Schema

NameRequiredDescriptionDefault
yogaNoOptional. Part of a yoga's name, for example "Gajakesari" or "Raja", to show only the yogas that match.
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered; the description goes further by disclosing the exact return payload — planets, houses, classical text and verse, textual result, one of six named statuses with last/next runs, and Mahadasha/Antardasha periods with start, end, and length. It also flags a non-obvious edge behavior: dormant yogas are listed with a reason and no dates.

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 core action, then output shape, then usage triggers — a sound order. The middle sentence is a long comma-chained enumeration of return fields that could be split for scannability, but no sentence is filler given there is no output schema.

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 six parameters, no output schema, and time-period computation involved, the definition covers what an agent needs: the fields returned, the status vocabulary, the dormant-yoga exception, and when to invoke it. Nothing material about calling or interpreting the result is left unstated.

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% and the parameter docs are unusually thorough (date ambiguity, 12-hour time ambiguity, coordinate pairing), so the description adds no parameter-level meaning beyond the schema. Baseline 3 applies; at most it hints that a named yoga can be looked up, which maps loosely to the 'yoga' filter.

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 ('Finds the classical yogas formed in a birth chart') and enumerates concrete examples (Gajakesari, Budha-Aditya, Raja, Dhana, Pancha Mahapurusha). This clearly separates it from sibling tools such as check_doshas or check_sade_sati, which handle different chart verdicts.

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?

Gives three explicit user-question triggers ('which yogas they have', 'whether a named yoga is in their chart', 'when a yoga was or becomes active'), which is strong positive guidance. It stops short of naming when-not-to-use cases or pointing to an alternative tool, so it is not a full 5.

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