Skip to main content
Glama

Moon Dasha Vedic Astrology

Compatibility

compatibility
Read-onlyIdempotent

Match two people's Vedic charts with Moon Dasha: Guna Milan (Ashtakoota) out of 36 with each koota's points, the koota doshas and the Muhurta Chintamani conditions that lift them; each person's Mangal Dosha (outside the 36); and Dual Cosmodyne, a Western synastry score with its strongest aspects. Each score stands on its own. Needs both people's birth dates, local birth times and birthplaces (place_ids from find_place). Guna Milan reads one person as the groom and one as the bride, so it needs to know who is the man and who is the woman: ask if the person has not said, and set groom to the man's letter. With no genders given, or for a couple of the same sex, person A takes the groom's seat. The figures are Moon Dasha's calculations. A score shows how two charts agree by tradition, not whether a relationship will succeed; never treat it as a reason not to marry, never read Nadi as a medical or genetic test, 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": {
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
groomNoWhich person takes the groom's seat in Guna Milan. Default a. Set b only when the person has said that B is the man in a man-and-woman couple.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
person_aYesOne person: birth date, local birth time and birthplace.
person_bYesOne person: birth date, local birth time and birthplace.
aspect_descriptionsNoAdd a short description to each Dual Cosmodyne aspect listed. Set only when the person asks what the aspects mean.

Output Schema

NameRequiredDescriptionDefault
person_aYes
person_bYes
settingsYes
guna_milanYes
report_linkYes
dual_cosmodyneYes

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 a safe, idempotent, closed read, so the bar is lower; the description nonetheless adds real behavioral context: 'Each score stands on its own', that the figures are Moon Dasha's calculations, and explicit interpretive limits (not a predictor of relationship success, Nadi not a medical/genetic test). It does not discuss error behavior or what happens when a place_id is invalid, but the interpretive framing is unusually substantive.

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-loads the purpose and outputs, then moves to prerequisites, then the gender rule, then caveats — a logical order. It is on the long side and the final prohibition list (death, illness, markets, elections, court cases) runs past what this tool's inputs could produce, costing some tightness.

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?

An output schema exists, so return values need not be explained; the description instead covers the things structured fields cannot: input prerequisites, the groom-seat default logic, and interpretive boundaries. For a nested two-person input with an explicit ethical surface, nothing essential is missing.

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 baseline is 3. The description reinforces the groom rule and the place_id source, but adds nothing about the ayanamsa enum or aspect_descriptions beyond what the schema already documents.

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 ('Match two people's Vedic charts with Moon Dasha') and then enumerates the distinct outputs: Guna Milan out of 36 with per-koota points and doshas, Mangal Dosha outside the 36, and Dual Cosmodyne synastry aspects. This clearly separates it from sibling tools like birth_chart or strengths, which produce single-person output.

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 concrete preconditions ('Needs both people's birth dates, local birth times and birthplaces (place_ids from find_place)') and a decision rule for the groom seat, including the fallback when no genders are given or the couple is same-sex. It also states when to set aspect_descriptions and that ayanamsa defaults to Lahiri, though it never says when to prefer birth_chart or another sibling instead.

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