Skip to main content
Glama

Supastro

Find the current Vimshottari dasha

get_current_dasha
Read-onlyIdempotent

Calculates which Vimshottari dasha periods are running for a birth: the Mahadasha, Antardasha and Pratyantardasha lords with each period's start and end date. Use it when someone asks which dasha or planetary period they are in, or when it ends. Covers today by default, or another date after the birth. Returns period lords and dates only, with no interpretation. The dates move with the birth time.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. The day to check as YYYY-MM-DD. Defaults to today. Convert the person's own wording to this form; if an all-number date could be read two ways, ask which number is the day.
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the description correctly focuses on behavior the schema cannot express: the output is 'period lords and dates only, with no interpretation,' and 'The dates move with the birth time' warns that results are birth-time sensitive. That last point materially affects how an agent should treat uncertain birth times.

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?

Four short sentences in a sensible order: what it computes, when to use it, the default date behavior, then what is returned and the birth-time caveat. No filler, though the final sentence about dates moving with birth time could be folded into the return sentence.

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?

There is no output schema, and the description compensates by stating that only lords and dates come back with no interpretation, which prevents an agent from promising analysis. It also covers the default date and the birth-time sensitivity; only the relationship to the timeline sibling remains unaddressed.

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?

With 100% schema description coverage, the schema already documents the date default, coordinate pairing, and date-format ambiguity. The description adds little parameter-level meaning beyond 'Covers today by default' (already in the schema) and 'the dates move with the birth time'; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Calculates which Vimshottari dasha periods are running for a birth') and enumerates the three levels returned (Mahadasha, Antardasha, Pratyantardasha) with their start and end dates. An agent knows exactly what this produces, though nothing in the text distinguishes it from the sibling get_dasha_timeline.

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?

'Use it when someone asks which dasha or planetary period they are in, or when it ends' gives a clear triggering question type, and 'Covers today by default, or another date after the birth' scopes the date selection. It stops short of naming when to prefer get_dasha_timeline or another sibling, so it is strong context without explicit alternatives.

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