Skip to main content
Glama

Moon Dasha Vedic Astrology

Divisional charts

divisional_charts
Read-onlyIdempotent

Calculate Vedic divisional charts (vargas) with Moon Dasha: any of the 26 the moondasha.com report draws (D1, D9, D2, D3, D4, D7, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60, D5, D6, D8, D11, D72, D81, D108, D144, D150, D300; default the D9, Navamsa). Each chart gives its Ascendant and the nine grahas with sign, whole-sign house from that chart's own Ascendant, sign lord and relationship, dignity by sign, Vargottama and Bhavottama, what the chart is read for, and the span of birth times that keeps its Ascendant sign, plus a link to the charts on moondasha.com. The higher the division, the more exact the birth time must be: the D60 Ascendant changes sign every few minutes, and the D150's and the D300's within about a minute. Needs the birth date, the local birth time and the birthplace (a place_id from find_place); set time_is_approximate when the time is a guess. 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": "divisional_charts"
  }
}

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.
chartsNoThe divisional charts wanted, in order, any of D1, D9, D2, D3, D4, D7, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60, D5, D6, D8, D11, D72, D81, D108, D144, D150, D300 (D1 is the birth chart, for comparison). Default: the D9 (Navamsa) alone.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
d2_methodNoThe D2 (Hora) scheme: parashara (default; the Sun and Moon horas) or uma_shambhu. Set uma_shambhu only when the person asks for it.
chart_styleNoHow the card draws the charts: 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: each chart then says whether its houses hold an hour either side.

Output Schema

NameRequiredDescriptionDefault
birthYes
chartsYes
settingsYes
chart_linkYes
chart_styleYes

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 readOnly/idempotent/non-destructive/closed-world, so the safety bar is met. The description adds genuine behavioral context beyond them: the calculation source (Moon Dasha), sensitivity of high divisions to birth-time precision with concrete examples (D60 sign changes every few minutes, D150/D300 within a minute), and the output contents. The ethical-use caveat is useful but somewhat generic boilerplate.

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?

The paragraph is front-loaded with purpose, then requirements, then output, then caveats — a sensible order with no filler sentences. It loses a point for re-enumerating all 26 chart codes, which duplicates the enum already present in the input schema and burns tokens without adding selection guidance.

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 read-only calculation tool with 9 parameters, 100% schema coverage, and a declared output schema, this description covers everything the agent needs: inputs, the find_place prerequisite, default behavior, precision caveats, and interpretation limits. Nothing required to invoke it correctly 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 every parameter is already documented, making 3 the baseline. The description adds only modest extra meaning: the find_place dependency for place_id and the effect of time_is_approximate ("each chart then says whether its houses hold an hour either side"), while node, ayanamsa, d2_method and chart_style are left entirely to the schema.

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 description opens with a specific verb+resource ("Calculate Vedic divisional charts (vargas)"), names the full domain of 26 charts, and states the default (D9, Navamsa), while the schema notes D1 is the birth chart for comparison. An agent can distinguish this from siblings like birth_chart or planetary_positions without opening any other schema.

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 required inputs (birth date, local time, birthplace via find_place) and gives clear context on when a chart is trustworthy versus when precision matters, including setting time_is_approximate for guessed times. It stops short of explicitly contrasting with birth_chart (e.g., "use birth_chart for the D1-only view"), so no explicit exclusions are given.

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