Skip to main content
Glama

Supastro

List the full Vimshottari dasha timeline

get_dasha_timeline
Read-onlyIdempotent

Calculates the whole Vimshottari dasha timeline for a birth: every Mahadasha from birth across 120 years with start and end dates, and the nine Antardashas inside one Mahadasha. Use it when someone asks for their full dasha list, what comes after the current period, or the sub-periods of a named Mahadasha. The Antardashas shown are those of the Mahadasha running today unless another is named. Returns period lords and dates only. 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_dasha_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
mahadashaNoOptional. The Mahadasha whose Antardashas to list, by its lord, for example Saturn. Defaults to the Mahadasha running today.
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

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description nonetheless adds real behavioral context: output is period lords and dates only, and the dates shift with birth time. It does not describe pagination or ordering guarantees, but for a read-only calculation that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the core purpose, then usage triggers, then defaults and output shape. No filler or repetition; every sentence contributes a distinct fact an agent would otherwise have to infer.

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 the return shape (period lords and dates only) and the default-subperiod behavior. With full schema coverage on six parameters and safety annotations in place, the only lightly covered area is result size or ordering.

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% with detailed descriptions for every parameter, so the schema already carries most semantic weight. The description adds marginal value by explaining that Antardashas default to the Mahadasha running today and that birth time affects the returned dates, but it does not elaborate on parameter formats beyond what the schema states.

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 ("Calculates the whole Vimshottari dasha timeline") and specifies the output scope: every Mahadasha across 120 years with start and end dates plus nine Antardashas. This clearly separates it from get_current_dasha, since the description frames it as the full list rather than the period running today.

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 explicit trigger conditions - the user asks for their full dasha list, what comes after the current period, or the sub-periods of a named Mahadasha. It also states the default Antardasha selection when no Mahadasha is named, which prevents misuse. It stops short of naming an alternative sibling for the single-current-period case, so no explicit when-not or sibling routing is 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.

Resources