Sahadeva

Generate a complete evidence-linked life report

generate_full_life_report

Read-onlyIdempotent

EXPERT FULL-REPORT TOOL — prefer consult_jyotishya (brief dossier + profileRef) for normal questions; use get_full_life_report_section for one section at a time. Builds a complete South Indian astrology report covering all major life areas, domain-specific timing outlooks, measured strengths, Vargas, structural Yogas, current Dasha and upcoming Antardashas. Timing activation identifies an area, never a specific event; interpretations remain qualified and evidence-linked.

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	ISO date or instant for the current-timing section; defaults to now
`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
`safety`	Yes
`anchors`	Yes
`aspects`	Yes
`subject`	Yes
`placements`	Yes
`uncertainty`	Yes
`ashtakavarga`	Yes
`futureTiming`	No
`currentTiming`	Yes
`schemaVersion`	Yes
`sourceCoverage`	Yes
`measuredStrengths`	Yes
`plainLanguageReading`	Yes
`divisionalChartAnchors`	Yes

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"
+]

Changed1 schema field changedOct 15, 2026
- addedOutput schema / properties / futureTiming
```
Added value: +{
+  "type": "object"
+}
```
First observedOct 1, 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, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that — the caveat that timing activation identifies an area and never a specific event, and that interpretations are qualified and evidence-linked. It omits cost/latency expectations for a full report, which keeps it from a 5.

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?

Front-loaded with the routing decision before the content scope, and the three sentences carry distinct information. The 'EXPERT FULL-REPORT TOOL' label is mildly redundant with the rest but earns its place by signaling weight/priority.

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, and the report's scope is well covered. However, for a 13-parameter tool with 31% schema coverage, the description leaves the input contract under-explained, which is a real completeness gap.

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?

Schema description coverage is only 31% across 13 parameters, and the description supplies no parameter guidance at all — nothing on date/time, place vs. explicit coordinates, focus, horizonYears, or birthTimeAccuracyMinutes. With such low coverage the description should compensate, and it does not.

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 (builds/generates) and resource (complete South Indian astrology report) and enumerates the covered content — life areas, timing outlooks, strengths, Vargas, Yogas, Dasha/Antardashas. It explicitly distinguishes itself from consult_jyotishya and get_full_life_report_section, so an agent can route without opening another 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?

Gives explicit when-to-use routing: prefer consult_jyotishya for normal questions and get_full_life_report_section for a single section. It effectively positions itself as the heavyweight full-scope option, so when and when-not are both clear.

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.