Skip to main content
Glama

Moon Dasha Vedic Astrology

Planet and house strengths

strengths
Read-onlyIdempotent

Calculate Vedic planet and house strengths with Moon Dasha, as the moondasha.com report computes them: Shadbala (each planet's six-fold strength in virupas and rupas against its required minimum, with Ishta and Kashta Phala), Bhava Bala (each house's strength), Ashtakavarga (bindus by sign for each planet and the Sarvashtakavarga, by Varahamihira's or Parashara's tables), Vimsopaka Bala and Vaiseshikamsa Bala (under the 6, 7, 10 and 16 chart schemes), each with the report's own reading bands, plus a link to them on moondasha.com. Choose with include; all five by default. Needs the birth date, the local birth time and the birthplace (a place_id from find_place). 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": "strengths"
  }
}

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.
includeNoWhich strengths to give, any of shadbala (with Ishta and Kashta Phala), bhava_bala (house strength), ashtakavarga, vimsopaka and vaiseshikamsa. Default: all five.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
ashtakavarga_methodNoWhose Ashtakavarga tables: varahamihira (default) or parashara. Set parashara only when the person asks for Parashara's tables.
time_is_approximateNoSet when the birth time is a guess. The strengths are computed for the time given.

Output Schema

NameRequiredDescriptionDefault
birthYes
includeYes
settingsYes
shadbalaYes
vimsopakaYes
bhava_balaYes
chart_linkYes
ashtakavargaYes
vaiseshikamsaYes
noon_centred_dayYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context on top: the figures are Moon Dasha's specific calculations, come with the report's own reading bands, link back to moondasha.com, and are computed for the time given (with time_is_approximate noted). It does not discuss failure modes or precision limits beyond that.

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?

Purpose and output list are front-loaded, and the per-subsystem glosses ('six-fold strength in virupas and rupas against its required minimum') genuinely add meaning beyond the bare enum values. It is still one dense paragraph with some duplication of schema enum values, so it is efficient but not maximally scannable.

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 an 8-parameter read-only computation with a full schema and an output schema, nothing essential is missing: provenance, required inputs, defaults, the report link, and interpretation cautions are all stated, so the agent can call it correctly and use the result responsibly.

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 all eight parameters are documented there, so baseline is 3. The description only restates the include default and the Varahamihira/Parashara table choice; it adds nothing on ayanamsa, node, or time_is_approximate beyond what the schema already says.

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 ('Calculate Vedic planet and house strengths with Moon Dasha') and then enumerates the five distinct outputs (Shadbala, Bhava Bala, Ashtakavarga, Vimsopaka, Vaiseshikamsa) with enough detail that an agent can tell this apart from siblings like birth_chart or divisional_charts without opening a 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?

Gives concrete prerequisites ('Needs the birth date, the local birth time and the birthplace (a place_id from find_place)'), a default rule ('Choose with include; all five by default'), and guardrails on interpretation. It stops short of an explicit when-to-use-this-instead-of-X rule against birth_chart or divisional_charts, so it is clear context rather than full 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