Skip to main content
Glama

ERUX Astrology & Ephemeris Engine

calculate_dasha

Read-onlyIdempotent

Calculate the classical Parashara Vimshottari Dasha planetary timeline (120-year cycle) for a person or founding event. Corresponds to the /dasha slash command. Requires birth date ('date', YYYY-MM-DD), birth time ('time', HH:MM, default '12:00'), and birth city ('city'). Returns current Mahadasha and Antardasha periods, active dates, psychological and karmic significance, upcoming macro-epochs, and a direct link to the interactive ERUX Dasha calendar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_dasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoNatal birth city (e.g. 'London', 'Kanpur')
dateNoNatal birth date in YYYY-MM-DD format (e.g. '1992-10-24')
timeNoNatal birth time in 24-hour HH:MM format (default '12:00')12:00
countryNoCountry of birth to disambiguate city
birth_cityNoExplicit alias for natal birth city
birth_dateNoExplicit alias for natal birth date (YYYY-MM-DD)
birth_timeNoExplicit alias for natal birth time (HH:MM)
target_dateNoTarget historical or future evaluation date (YYYY-MM-DD, defaults to current date)
birth_countryNoExplicit alias for natal birth country

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / user_prompt
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Raw user query for intent arbitration",
      -  "title": "User Prompt"
      -}
  2. Changed10 schema fields changed
    • addedInput schema / properties / birth_city / description
      Added value: +"Explicit alias for natal birth city"
    • addedInput schema / properties / birth_country / description
      Added value: +"Explicit alias for natal birth country"
    • addedInput schema / properties / birth_date / description
      Added value: +"Explicit alias for natal birth date (YYYY-MM-DD)"
    • addedInput schema / properties / birth_time / description
      Added value: +"Explicit alias for natal birth time (HH:MM)"
    • addedInput schema / properties / city / description
      Added value: +"Natal birth city (e.g. 'London', 'Kanpur')"
    • addedInput schema / properties / country / description
      Added value: +"Country of birth to disambiguate city"
    • addedInput schema / properties / date / description
      Added value: +"Natal birth date in YYYY-MM-DD format (e.g. '1992-10-24')"
    • addedInput schema / properties / target_date / description
      Added value: +"Target historical or future evaluation date (YYYY-MM-DD, defaults to current date)"
    • addedInput schema / properties / time / description
      Added value: +"Natal birth time in 24-hour HH:MM format (default '12:00')"
    • addedInput schema / properties / user_prompt / description
      Added value: +"Raw user query for intent arbitration"
  3. First observed

TDQS

A4/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 semantics, so the description's added value is the output shape: Mahadasha/Antardasha periods, active dates, interpretation, and a calendar link. It also discloses the '12:00' time default, which materially affects results. It does not mention precision caveats for unknown birth times or any auth/rate constraints.

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?

Three front-loaded sentences covering purpose, inputs, and outputs with no filler. The return-value enumeration is somewhat list-like and partially redundant given an output schema exists, but it stays compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Strong overall given rich annotations and a full output schema, but the description leaves real gaps: nine parameters exist yet only three are discussed, and the alias-vs-primary field interaction is never explained. An agent must consult the schema to learn that nothing is actually required and that target_date controls the evaluation epoch.

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 coverage is 100%, so the baseline is 3. The description restates date/time/city formats but omits the alias parameters (birth_date, birth_time, birth_city, birth_country) and target_date entirely, and its 'Requires birth date...' language conflicts with the schema where required is empty and all parameters are optional.

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 the classical Parashara Vimshottari Dasha planetary timeline'), including the 120-year cycle scope and that it applies to a person or founding event. An agent can distinguish this from calculate_chart or get_horoscope without opening the 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 clear usage context by listing the required natal inputs and noting the equivalence to the /dasha slash command, which helps an agent map a user request. It stops short of naming when to prefer calculate_chart or get_horoscope instead, so no exclusions or sibling routing are provided.

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.