Sahadeva

Calculate Varshaphal annual chart

calculate_varshaphal

Read-onlyIdempotent

Casts the sidereal (Lahiri) solar-return chart for a target year and returns Tajaka Varshaphal: Muntha, the five office-bearers with Panchavargiya and Harsha Bala, the year lord, the sixteen Tajaka yogas, cited Sahams (Punya first), and Mudda and Patyamsa dashas.

Input Schema

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

Output Schema

Name	Required	Description	Default
`muntha`	Yes
`safety`	Yes
`status`	Yes
`tajika`	Yes
`sources`	No
`subject`	Yes
`annualChart`	Yes
`conventions`	No
`solarReturn`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026
- addedOutput schema / properties / conventions
```
Added value: +{
+  "type": "array"
+}
```
- changedOutput schema / properties / schemaVersion / const
```
Previous value: -"sahadeva-varshaphal-1"New value: +"sahadeva-varshaphal-2"
```
- addedOutput schema / properties / sources
```
Added value: +{
+  "type": "array"
+}
```

Changed1 schema field changedOct 15, 2026

changedInput schema / required

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

AddedOct 15, 2026

TDQS

B3.3/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, so the safety profile is covered. The description does add one genuinely useful convention — the Lahiri sidereal ayanamsa — but the rest is an enumeration of return contents that the output schema already carries, and it says nothing about computation caveats or input requirements.

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?

A single front-loaded sentence that opens with the verb and keeps no filler. The trailing list of output artifacts is dense and partially redundant with the output schema, which slightly dilutes it, but nothing is wasted.

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?

The output schema lets the description skip explaining return values, and annotations carry the safety profile, but for an 11-parameter tool with 27% schema coverage the description leaves the input contract underexplained. Nothing tells the agent about the place-or-coordinates requirement or the timezone dependency, which are the hardest parts of calling this tool correctly.

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 11 parameters and only 27% schema description coverage, the description must compensate, and it does not. It never touches date, time, targetYear, the place/latitude/longitude/timezone alternative, language, or birthTimeAccuracyMinutes; only 'for a target year' faintly gestures at targetYear.

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 ('Casts the sidereal (Lahiri) solar-return chart for a target year') and then enumerates the exact Tajaka Varshaphal deliverables. An agent can distinguish this from siblings like calculate_dasha_system or calculate_gochara without opening any schema, since 'annual solar-return chart' is a distinct chart type.

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 when-to-use or when-not-to-use guidance and no named alternative. The description never mentions the place-vs-coordinates branching in the schema, nor prerequisites like birth date/time accuracy, so the agent must infer everything from structured fields.

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.