Skip to main content
Glama

Cosmic Chemistry

Current dasha (Vimshottari)

current_dasha
Read-onlyIdempotent

Use this when someone asks which mahadasha or antardasha they are running, their Vimshottari dasha timeline, when their next dasha begins, or when a dasha ends ("when does my Rahu dasha end", "my current dasha lord", "which dasha was I in during 2019", "when is my Venus antardasha"). Returns every mahadasha with dates, and the antardasha, pratyantar and sookshma running now. Set on_date for what was or will be running on another day; set mahadasha to list all nine antardashas of one mahadasha with dates. For what a dasha means in general, without birth details, use mahadasha_meaning. Needs birth date, time and town, and a past birth: it counts from today.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "current_dasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
on_dateNoOptional: a day as YYYY-MM-DD, to see which periods were or will be running then. Leave out for today.
mahadashaNoOptional: one mahadasha lord, to list all nine antardashas of that mahadasha with dates, past, now or ahead.
birth_dateYesDate of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_timeYesLocal clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_placeYesTown or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mahadasha
      Added value: +{
      +  "description": "Optional: one mahadasha lord, to list all nine antardashas of that mahadasha with dates, past, now or ahead.",
      +  "enum": [
      +    "sun",
      +    "moon",
      +    "mars",
      +    "mercury",
      +    "jupiter",
      +    "venus",
      +    "saturn",
      +    "rahu",
      +    "ketu"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / on_date
      Added value: +{
      +  "description": "Optional: a day as YYYY-MM-DD, to see which periods were or will be running then. Leave out for today.",
      +  "type": "string"
      +}
  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 a safe read-only, idempotent, closed-world operation, so the safety bar is covered; the description then adds materially new behavior: the returned depth (mahadasha dates plus antardasha, pratyantar and sookshma currently running) and the accuracy demand on birth_time. The phrase "and a past birth: it counts from today" is awkward and slightly obscure about why a past birth date is required, which keeps it from a 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 the usage triggers and examples, then the return shape, then the alternative tool, then prerequisites — a sensible order with no filler sentences. The parenthetical query examples are useful but slightly long, keeping it just below maximum.

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?

For a read-only calculation tool with no output schema, the description covers what is returned, at what granularity, and what inputs are mandatory. The one soft spot is the unexplained dependency on a non-future birth date, which an agent might need spelled out more plainly.

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 explains on_date, mahadasha (with enum values), birth_date, birth_time and birth_place in nearly the same words. The description reinforces intent (on_date for another day, mahadasha for all nine antardashas) but adds little semantics beyond the schema, so the baseline 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?

The description states a specific verb and resource — it returns the Vimshottari mahadasha/antardasha timeline with dates — and anchors it in recognizable user phrasings ("my current dasha lord", "when does my Rahu dasha end"). It also names the sibling mahadasha_meaning and the condition that selects it, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Concrete when-to-use triggers are given (current period, timeline, start/end dates, historical period, single-mahadasha breakdown), plus explicit routing to mahadasha_meaning for general meaning without birth details. It also states prerequisite data (birth date, time and town) and when to prefer the on_date and mahadasha options.

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