AstroNest — Vedic Astrology & Ephemeris

Vimśottarī daśā timeline (planetary periods)

get_dasha

Read-onlyIdempotent

Use this when the user asks which planetary period (daśā) they are in, when it ends, or which periods are coming. The current periods include the running pratyantardaśā; send depth 'pratyantardasha' for the full timeline at that level. Cost: 1 credit per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209}}

Input Schema

Name	Required	Description	Default
`depth`	No	Timeline depth. 'pratyantardasha' nests the pratyantardaśās under each antardaśā (about ten times larger). The current periods always include the running pratyantardaśā.	antardasha
`birthData`	Yes	The person's birth data: date, local time (omit if unknown), IANA timezone, latitude and longitude.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026

addedInput schema / properties / depth

Added value: +{
+  "default": "antardasha",
+  "description": "Timeline depth. 'pratyantardasha' nests the pratyantardaśās under each antardaśā (about ten times larger). The current periods always include the running pratyantardaśā.",
+  "enum": [
+    "antardasha",
+    "pratyantardasha"
+  ],
+  "type": "string"
+}

addedOutput schema / $defs / CurrentDasha / properties / pratyantardasha

Added value: +{
+  "description": "The running pratyantardaśā.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / $defs / CurrentDasha / properties / pratyantardashaEnd
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / $defs / DashaPeriod / properties / pratyantardashas

Added value: +{
+  "description": "On each antardaśā when depth is 'pratyantardasha'.",
+  "items": {
+    "$ref": "#/$defs/DashaPeriod"
+  },
+  "type": "array"
+}

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds genuinely new operational facts: 1 credit per call, only successful calls charged, sandbox key free with fixed sample, and deterministic results. That is meaningful context beyond the structured fields, though it says nothing about auth or rate limits.

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, front-loaded with the trigger condition, followed by depth guidance, cost, determinism, and an example. Every line carries information, though the example-arguments block partially duplicates what the schema already specifies.

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

Completeness5/5

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

With an output schema present and rich annotations, the description only needs to cover selection, cost, and determinism — all of which it does. Nested birthData structures are documented in the schema, so nothing an agent needs to call the tool correctly is missing.

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 baseline is 3, but the description adds a subtlety the schema does not state as directly: current periods always include the running pratyantardaśā, and requesting depth 'pratyantardasha' expands the timeline roughly tenfold. This helps an agent pick a depth value correctly.

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?

States a specific verb+resource: retrieving the Vimśottarī daśā timeline of planetary periods, with scope framed by the user's question ('which planetary period they are in, when it ends, or which are coming'). It is clear without opening the schema, though it does not explicitly distinguish itself from potentially overlapping siblings like get_domain_timeline or resolve_timing.

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 concrete trigger conditions tied to user intent ('when the user asks which planetary period...'), plus a decision rule for the depth parameter. No explicit when-not or alternative-tool guidance, which keeps it out of 5 territory.

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

All AstroNest — Vedic Astrology & Ephemeris tools Inspect

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.