Skip to main content
Glama

Moon Dasha Vedic Astrology

Birth chart

birth_chart
Read-onlyIdempotent

Calculate a Vedic birth chart (D1, sidereal) with Moon Dasha: the ascendant and the nine grahas with sign, degree, whole-sign house, nakshatra and pada, nakshatra lord, dignity, sign lord and the planet's relationship to it, retrograde, combust, Vargottama and Bhavottama flags, and chara karakas (7-karaka scheme), plus a link to the full chart on moondasha.com. Needs the birth date, the local birth time and the birthplace (a place_id from find_place). If the person does not know the birth time, ask for a best guess and set time_is_approximate. The figures are Moon Dasha's calculations. Interpret them with care 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": "birth_chart"
  }
}

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.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
chart_styleNoHow the chart card draws the chart: North Indian (default) or South Indian. Set south only when the person asks for it.
time_is_approximateNoSet when the birth time is a guess: the answer then shows the ascendant an hour either side.

Output Schema

NameRequiredDescriptionDefault
birthYes
bodiesYes
summaryYes
settingsYes
chart_linkYes
chart_styleYes
ascendant_windowYes

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 a safe, idempotent, closed-world read, so the description's job is additive context — and it delivers provenance ('The figures are Moon Dasha's calculations'), a returned link to the full chart, the consequence of time_is_approximate (ascendant shown an hour either side), and explicit interpretation guardrails. It omits any note on cost, latency, or failure modes for bad place_ids.

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 calculation and its output set, followed by prerequisites and guidance in a logical order. The long enumeration of chart artifacts is dense and partly duplicative of the output schema, but it does orient the agent on what to report.

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?

For a 7-parameter tool with a rich output schema, the description covers everything selection depends on: what it computes, required inputs, the cross-tool dependency on find_place, unknown-time handling, provenance, and interpretation limits. Return values are covered by the output schema, so nothing material 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% and the schema already documents defaults for node, ayanamsa, and chart_style, plus the time_is_approximate prompt and the find_place origin of place_id. The description largely restates the required trio rather than adding syntax or edge-case meaning, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Calculate a Vedic birth chart (D1, sidereal) with Moon Dasha') and enumerates the produced artifacts, so an agent knows exactly what the tool returns. The D1/sidereal framing also implicitly separates it from sibling tools like divisional_charts and planetary_positions.

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 prerequisites (birth date, local time, place_id from find_place) and an explicit fallback path when the time is unknown: ask for a best guess and set time_is_approximate. It never states when to prefer a sibling such as divisional_charts or planetary_positions, so it stops short of full alternative routing.

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