Sahadeva

Get complete one-shot reading context

get_full_reading_context

Read-onlyIdempotent

EXPERT FULL-REPORT ALIAS — prefer consult_jyotishya for normal questions. One-call alias for the complete evidence-linked life report. Returns enriched placements, strengths, Vargas, synthesis, current Dasha, and a configurable future transit-and-Dasha horizon for narration clients.

Input Schema

Name	Required	Description	Default
`date`	Yes
`name`	No
`time`	Yes
`focus`	No		general
`place`	No	Catalogue query or display label when explicit coordinates are supplied
`asOfDate`	No
`language`	No		en
`latitude`	No
`timezone`	No	Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata
`longitude`	No
`horizonYears`	No
`timezoneOffset`	No	Optional fallback offset; derived from timezone and the requested local date when omitted
`birthTimeAccuracyMinutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 18, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "place"
+    ]
+  },
+  {
+    "required": [
+      "latitude",
+      "longitude",
+      "timezone"
+    ]
+  }
+]

addedInput schema / properties / latitude / maximum
```
Added value: +90
```
addedInput schema / properties / latitude / minimum
```
Added value: +-90
```
addedInput schema / properties / longitude / maximum
```
Added value: +180
```
addedInput schema / properties / longitude / minimum
```
Added value: +-180
```

addedInput schema / properties / place / description

Added value: +"Catalogue query or display label when explicit coordinates are supplied"

addedInput schema / properties / timezone / description

Added value: +"Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata"

addedInput schema / properties / timezoneOffset / description

Added value: +"Optional fallback offset; derived from timezone and the requested local date when omitted"

addedInput schema / properties / timezoneOffset / maximum
```
Added value: +14
```
addedInput schema / properties / timezoneOffset / minimum
```
Added value: +-14
```

changedInput schema / required

Previous value: -[
-  "date",
-  "time",
-  "place",
-  "latitude",
-  "longitude",
-  "timezoneOffset"
-]New value: +[
+  "date",
+  "time"
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "time",
-  "place",
-  "latitude",
-  "longitude",
-  "timezoneOffset"
-]New value: +[
+  "date",
+  "time",
+  "place",
+  "latitude",
+  "longitude",
+  "timezoneOffset"
+]

AddedOct 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the output content and the 'narration clients' purpose plus the configurable horizon, but says nothing about rate limits, auth, or latency concerns. Modest value beyond annotations.

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?

It is two sentences, front-loads the alias/routing caveat before the return summary, and wastes little. The all-caps lead-in is a minor style cost but it does front-load the most decision-relevant fact.

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

Completeness2/5

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

For a 13-parameter tool with an anyOf location mode and a partial-required set, the description leaves the agent without guidance on how to supply birth data versus coordinates. The presence of an output schema excuses it from explaining returns, but not from the parameter-level gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 13 parameters at 23% schema description coverage, the description needs to compensate for the documentation gap but largely does not. Only the future horizon is alluded to ('configurable... horizon'); birth date/time, the place-vs-coordinates anyOf, focus, language, and accuracy parameters get no explanatory text.

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 role (one-call alias for the complete evidence-linked life report) and enumerates what it returns at a high level (placements, strengths, Vargas, synthesis, Dasha, transit horizon). It also distinguishes itself from the similar sibling consult_jyotishya, so an agent can tell them apart without opening a 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?

It explicitly tells the agent to 'prefer consult_jyotishya for normal questions,' naming the alternative and the condition that selects it, and signals its own niche as an expert/narration path. This is exactly the when-not/alternative routing guidance the dimension asks for.

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.