Sahadeva

Calculate a declared Dasha system

calculate_dasha_system

Read-onlyIdempotent

A DASHA SYSTEM. Vimshottari (5 levels at asOfIso), Yogini, Ashtottari, Kalachakra, Narayana or Chara, with the period running at asOfIso and a timeline focused around it (detail: full returns every level).

Input Schema

Name	Required	Description
`date`	Yes	Birth date YYYY-MM-DD (1800–2050)
`name`	No	Person's name or a label
`time`	Yes	Local birth time HH:MM (24-hour); 6:30 PM is also accepted
`place`	No	Catalogue query or display label when explicit coordinates are supplied
`detail`	No	focused (default) keeps sub-periods only around asOfIso
`system`	Yes
`asOfIso`	Yes	ISO date-time whose running period is reported
`latitude`	No
`timezone`	No	Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata
`longitude`	No
`timezoneOffset`	No	Optional fallback offset; derived from timezone and the requested local date when omitted

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 18, 2026

addedInput schema / properties / asOfIso / description

Added value: +"ISO date-time whose running period is reported"

addedInput schema / properties / date / description

Added value: +"Birth date YYYY-MM-DD (1800–2050)"

addedInput schema / properties / date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

addedInput schema / properties / detail

Added value: +{
+  "description": "focused (default) keeps sub-periods only around asOfIso",
+  "enum": [
+    "focused",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / name / description
```
Added value: +"Person's name or a label"
```

addedInput schema / properties / time / description

Added value: +"Local birth time HH:MM (24-hour); 6:30 PM is also accepted"

Changed1 schema field changedOct 15, 2026

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "time",
-  "system",
-  "asOfIso"
-]New value: +[
+  "date",
+  "time",
+  "system",
+  "asOfIso"
+]

First observedOct 1, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context about output shape ('period running at asOfIso', 'detail: full returns every level'), but does not explain anything further such as computation scope or failure modes.

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

Conciseness2/5

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

The text is short, but the leading fragment 'A DASHA SYSTEM.' is not a coherent sentence and does not earn its place, leaving the reader without a clear front-loaded statement of what the tool does. The remainder is densely parenthetical rather than well structured.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for an 11-parameter tool with a non-trivial anyOf location requirement, the description omits how location inputs work and does not clearly delimit its scope against the many calculation siblings.

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 73%, so the schema documents most parameters and the baseline is 3. The description does add meaning beyond the schema for two parameters (the '5 levels' for Vimshottari at asOfIso and the focused/full behavior of detail), but leaves the anyOf location requirement (place vs latitude/longitude/timezone) unaddressed.

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

Purpose3/5

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

The description opens with the fragment 'A DASHA SYSTEM.' rather than a clear verb+resource, so the actual action (calculating a dasha timeline) is only inferable from the title. It lists the supported systems, which helps, but it never states what the tool produces and gives no differentiation from siblings like query_vimshottari_date.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool versus alternatives such as query_vimshottari_date, calculate_jaimini, or calculate_kp. No prerequisites, no when-not conditions, and no mention of the required birth data or location inputs.

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

All Sahadeva 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.