Skip to main content
Glama
arthiqlabs

Vedaksha

by arthiqlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

compute_drishti

Read-only

Calculate Vedic sign-based aspects (drishti) for all nine grahas, returning each aspect's graded strength and house distance. Use it to determine which planets aspect which signs and how strongly.

Instructions

Compute graha drishti — Vedic sign aspects — for all nine grahas. Unlike Western aspects, drishti is cast from sign to sign and is asymmetric: every graha aspects the 7th from itself, and Mars additionally aspects the 4th and 8th, Jupiter the 5th and 9th, Saturn the 3rd and 10th. Returns each aspect with its graded strength (Full, ThreeQuarter, Half, Quarter) and the house distance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sunYesSidereal longitude of Sun [0, 360)
ketuYesSidereal longitude of Ketu [0, 360)
marsYesSidereal longitude of Mars [0, 360)
moonYesSidereal longitude of Moon [0, 360)
rahuYesSidereal longitude of Rahu [0, 360)
venusYesSidereal longitude of Venus [0, 360)
saturnYesSidereal longitude of Saturn [0, 360)
jupiterYesSidereal longitude of Jupiter [0, 360)
mercuryYesSidereal longitude of Mercury [0, 360)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
aspectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv8.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "aspects": {
+      "items": {
+        "properties": {
+          "aspected_sign": {
+            "description": "Rashi receiving the drishti.",
+            "type": "integer"
+          },
+          "aspecting_planet": {
+            "description": "Graha casting the drishti.",
+            "type": "string"
+          },
+          "aspecting_sign": {
+            "description": "Rashi it occupies, 0=Aries … 11=Pisces.",
+            "type": "integer"
+          },
+          "houses_away": {
+            "description": "Count from the aspecting rashi, 1-12.",
+            "type": "integer"
+          },
+          "strength": {
+            "description": "Classical share cast: Full, ThreeQuarter, Half or Quarter.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "aspecting_planet",
+          "aspecting_sign",
+          "aspected_sign",
+          "houses_away",
+          "strength"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "aspects"
+  ],
+  "type": "object"
+}
  2. First observedv7.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already signal readOnlyHint=true; the description adds substantial behavioral detail beyond that: every graha aspects the 7th, Mars/Jupiter/Saturn have extra aspects, and the output includes graded strength and house distance. This gives a clear model of what happens when the tool is invoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states the operation and scope first, then presents the key asymmetric rules and output shape. Every sentence contributes useful information with no filler.

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

Completeness5/5

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

Given the read-only annotation, complete parameter schema, and output schema, the description supplies the remaining essential context: the Vedic drishti model, special aspect rules, and returned strength/distance values. An agent has enough information to select and call this tool correctly.

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 100% and every parameter is documented with the same format and range, so the description does not need to add much. The phrase 'for all nine grahas' maps to the required parameters but adds no semantic detail beyond the schema.

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?

The description clearly states the operation: 'Compute graha drishti — Vedic sign aspects — for all nine grahas,' giving a specific verb, resource, and full scope. It differentiates from Western aspects and lists the unusual aspect rules, but it does not explicitly name or distinguish a sibling tool.

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

Usage Guidelines4/5

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

It provides clear usage context by explaining that drishti is sign-to-sign, asymmetric, and has special extra aspects for Mars, Jupiter, and Saturn, while contrasting with Western aspects. However, it never names an alternative tool or states a when-not-to-use condition, so it lacks explicit routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools