Sahadeva

analyze spiritual path

analyze_spiritual_path

Read-onlyIdempotent

Evidence-linked analyze spiritual path without deterministic outcome claims.

Input Schema

Name	Required	Description
`date`	Yes
`name`	No
`time`	Yes
`place`	No	Catalogue query or display label when explicit coordinates are supplied
`topics`	No
`asOfIso`	No
`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.

Changed1 schema field changedOct 15, 2026

changedInput schema / required

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

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / topics / items / enum

Previous value: -[
-  "career",
-  "education",
-  "property",
-  "relationships",
-  "spirituality",
-  "wealth"
-]New value: +[
+  "career",
+  "education",
+  "property",
+  "relationships",
+  "spirituality",
+  "wealth",
+  "health",
+  "children"
+]

First observedOct 1, 2026

TDQS

D1.8/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds two useful behavioral notes – 'evidence-linked' and no deterministic outcome claims – but does not explain what evidence linkage means in practice or how outputs are constrained.

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 single sentence is too short for a tool of this complexity; it under-specifies rather than being concise, and the qualifiers are not front-loaded with actionable scope.

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

Completeness1/5

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

For a 10-parameter analytical tool with many siblings and low schema description coverage, the description is inadequate. Output schema existence relieves return-value explanation, but usage, scope, and parameter semantics are missing.

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

Parameters1/5

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

With 10 parameters and only 30% schema description coverage, the description supplies no parameter meaning at all (date, time, place, topics, coordinates/timezone, asOfIso, etc.). It fails to compensate for the low coverage.

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

Purpose2/5

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

The description is essentially the tool name and title reworded ('analyze spiritual path') with two qualifiers, so it is tautological rather than stating a specific analytical operation. It does not distinguish this tool from siblings like analyze_chart_topic or analyze_house.

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

Usage Guidelines1/5

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

No when-to-use, prerequisites, alternatives, or exclusions are given. The phrase 'without deterministic outcome claims' is a constraint, not usage guidance.

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.