Skip to main content
Glama

Moon Dasha Vedic Astrology

Yogas and doshas

yogas
Read-onlyIdempotent

List the yogas and doshas in a Vedic chart with Moon Dasha's yoga engine: each formed yoga and dosha with its strength (Moon Dasha's 0 to 5 index, not a probability), how it formed in this chart, any cancellations, its meaning and the planets whose periods it shows most in; weak yogas by name; cancelled doshas with what cancelled them; and the named doshas that are not present, such as Mangal Dosha or Kala Sarpa. Reads the birth chart (D1) or a divisional chart (varga). Needs the birth date, the local birth time and the birthplace (a place_id from find_place). The findings are Moon Dasha's calculations; interpret them as tendencies and never predict death, illness, a child's sex, markets, elections or court cases.

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": {
      "date": "<date>",
      "time": "<time>",
      "place_id": "<place_id>"
    },
    "name": "yogas"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
nodeNoRahu and Ketu by the mean node (default) or the true node.
timeYesLocal clock time at the birthplace, 24-hour HH:MM or HH:MM:SS. Required: if the person does not know it, ask for their best guess and set time_is_approximate.
vargaNoThe chart to read: D1, the birth chart (default), or a divisional chart such as D9 (Navamsa) or D10 (Dasamsa). Set only when the person asks about a divisional chart.
genderNoThe person's sex, for the few yogas whose rule depends on it (Maha Bhagya). Set only when the person has said; without it those yogas are left out.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
time_is_approximateNoSet when the birth time is a guess: the answer then names the yogas and doshas that would appear or disappear an hour either side.

Output Schema

NameRequiredDescriptionDefault
birthYes
notesYes
vargaYes
yogasYes
doshasYes
genderYes
settingsYes
chart_linkYes
weak_yogasYes
approximateYes
not_presentYes
cancelled_doshasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, non-destructive read, so the bar is lower, yet the description still adds real value: the strength figure is 'Moon Dasha's 0 to 5 index, not a probability,' the findings are 'Moon Dasha's calculations,' and results should be framed as tendencies. It also flags the ethical guardrails (never predict death, illness, a child's sex, markets, elections or court cases) that no annotation conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the closing caution is well placed, but the lead sentence is a roughly 100-word run-on enumerating every returned field, much of which duplicates the existing output schema. It would read better split into a short purpose line plus a compact list of what each result carries.

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?

Given eight parameters, four enums, and an output schema, the description still covers the key operational facts an agent needs (required inputs, find_place dependency, varga scoping, approximation handling) plus interpretation guidance. The main gap is the lack of explicit routing versus sibling tools for chart-reading requests.

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 baseline is 3, but the description goes beyond it by linking place_id to find_place and explaining what the output contains when gender is absent (those yogas are left out) and why time matters. It adds interpretive meaning to the 0-5 strength scale and the absence/cancellation categories rather than just restating field descriptions.

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 opening clause names a specific verb and resource: 'List the yogas and doshas in a Vedic chart with Moon Dasha's yoga engine.' It immediately distinguishes this from siblings such as birth_chart, strengths, or divisional_charts by scoping to formed yogas and doshas plus their cancellations and absences.

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?

It states the prerequisites clearly ('birth date, the local birth time and the birthplace (a place_id from find_place)'), which routes the agent to find_place first, and the schema's varga field notes to set it 'only when the person asks about a divisional chart.' What's missing is an explicit contrast with siblings like strengths or birth_chart, so the agent must infer that this is the yoga/dosha-specific read.

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