Skip to main content
Glama
Sign In

AstroCalc: Vedic astrology

by in.astrocalc
OverviewDiscussionsAdmin

What life phase (dasha) someone is in and what changes next

explain_dasha
Read-onlyIdempotent

Explains the life phase a person is in right now, what it tends to bring, when it ends and what comes next, from their birth details; or, without birth details, what a given phase means in general and how long it lasts. Useful when the user wonders why life feels a certain way at the moment, when things will change, or about timing for career, marriage, a move or a fresh start, for themselves or someone close to them. Also for direct questions: "what's my dasha", "which mahadasha am I in", "what's coming in my dasha", "meri dasha kaunsi chal rahi hai", "Shani ki mahadasha kab khatam hogi", "mera time kab badlega". Uses the Vimshottari dasha system. Two ways to call it: (1) with birth details (date, time, place) it returns the running Mahadasha and Antardasha with exact start/end dates, what the period is about for that chart and the next antardashas (AstroCalc engine); or (2) with lord (and optionally antardasha) set to a planet, e.g. lord "Saturn", antardasha "Venus", it returns the general meaning and length of that period, with no birth data needed. Birth details are not stored. Traditional information, not a prediction.

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": "explain_dasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoBirth latitude in decimal degrees (north positive). Give together with lon.
lonNoBirth longitude in decimal degrees (east positive). Give together with lat.
dateNoDate of birth, YYYY-MM-DD (Gregorian calendar).
langNoLanguage of the text fields: 'en' (English, default) or 'hi' (Hindi).
lordNoMahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given.
timeNoLocal clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'); '6:45 am' / '9:10 PM' also work. Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.
placeNoBirth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given.
antardashaNoOptional antardasha (sub-period) planet inside lord, e.g. "Venus".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / time / description
      Previous value: -"Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."New value: +"Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'); '6:45 am' / '9:10 PM' also work. Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
    • changedInput schema / properties / time / pattern
      Previous value: -"^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$"New value: +"^(([01]?\\d|2[0-3]):[0-5]\\d|(0?[1-9]|1[0-2]):[0-5]\\d ?[AaPp][Mm]|unknown)$"
  2. First observed

TDQS

A4.3/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 safety is covered; the description adds genuine context beyond that: the AstroCalc engine, exactly what the chart mode returns (running Mahadasha and Antardasha with start/end dates, next antardashas), that birth details are not stored, and a "traditional information, not a prediction" disclaimer. Output format and failure behavior are not described, which keeps it below 5.

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 purpose, then usage, then the two call modes enumerated as (1) and (2), which makes the dual-mode contract easy to scan. It runs long, with a lengthy multilingual list of example queries and some restatement of what the periods return, but the extra length is largely justified by the tool's two-mode complexity.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so adequately, telling the agent that chart mode yields Mahadasha/Antardasha with exact dates plus upcoming sub-periods. For an 8-parameter, dual-mode tool it is nearly complete; it omits error/ambiguous-place behavior and the shape of the general-meaning response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real relational semantics the schema does not convey as a whole: the two mutually exclusive invocation shapes (birth details vs. lord plus optional antardasha) and which one produces which kind of result. Individual defaults such as the unknown-time noon fallback remain schema-only.

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 ("Explains the life phase a person is in right now"), names the underlying system (Vimshottari dasha), and clearly separates two distinct modes: chart-based and lord-based. An agent can distinguish this from siblings like life_timeline or full_chart 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?

Rich when-to-use guidance: "why life feels a certain way at the moment, when things will change, or about timing for career, marriage, a move or a fresh start," plus concrete utterance examples in English and Hindi. It also explains which of the two call modes applies depending on whether birth details exist. It stops short of naming an alternative sibling tool or stating when NOT to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AstroCalc: Vedic astrology toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources