Sahadeva

Full classical remedy repertoire for a chart

build_remedy_repertoire

Read-onlyIdempotent

Full remedy repertoire. Works out each graha's functional nature and afflictions, then returns beej and Vedic mantras, stotra, gemstone (for grahas to strengthen), named daana, vrata, rudraksha, yantra, conduct, the Lal Kitab remedies for its fixed house, dosha remedies and Dasha-based timing. Every family is on by default; pass false to leave one out. No topic required.

Input Schema

Name	Required	Description	Default
`date`	Yes
`name`	No
`time`	Yes
`place`	No	Catalogue query or display label when explicit coordinates are supplied
`options`	No
`language`	No		en
`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
`birthTimeAccuracyMinutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 18, 2026
- changedInput schema / properties / options / properties / allowFasting / default
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / options / properties / allowGemstones / default
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / options / properties / allowMantras / default
```
Previous value: -falseNew value: +true
```
- removedInput schema / properties / options / properties / healthScreenedForFasting
```
Removed value: -{
-  "default": false,
-  "type": "boolean"
-}
```

Changed1 schema field changedOct 15, 2026

changedInput schema / required

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

AddedOct 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds genuinely new behavioral context by describing the computation pipeline and the default-on/exclude-with-false semantics of the remedy families. It does not discuss cost, rate limits, or output size, but the defaults behavior is the key trait an agent needs.

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?

The long opening sentence is dense but front-loaded with the output inventory, followed by two short sentences that carry the default/exclusion rule and the 'no topic required' cue. No sentence is filler, though the family list is heavy enough to slow scanning slightly.

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 no explanation, and the description covers what the tool produces and how to scope it. But for an 11-parameter tool with nested options and a place-versus-coordinates alternative, the description leaves the birth-data inputs entirely to the schema at 27% description coverage.

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 description coverage is only 27% across 11 params (including a nested options object), so the description carries some compensating burden. It does explain the options booleans collectively ('every family is on by default; pass false to leave one out'), but says nothing about date/time formats, the place-vs-coordinates alternative, language, or birthTimeAccuracyMinutes.

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 (works out each graha's functional nature and afflictions) and enumerates the concrete deliverables (beej/Vedic mantras, stotra, gemstone, daana, vrata, rudraksha, yantra, conduct, Lal Kitab remedies, dosha remedies, dasha timing), which separates it from narrow siblings like analyze_remedies or analyze_lal_kitab_remedies. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

'No topic required' implies a contrast with topic-driven tools, and 'Every family is on by default; pass false to leave one out' gives operational guidance for scoping the output. However, there is no explicit when-to-use-this-vs analyze_remedies / analyze_lal_kitab_remedies / suggest_safe_practice statement, so the agent must infer the routing.

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.