Skip to main content
Glama
arthiqlabs

Vedaksha

by arthiqlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

compute_gochara

Read-only

Calculate Gochara transit effects of seven planets against a chosen natal sign (Moon or Lagna), returning favorable/unfavorable verdicts and vedha obstructions per BPHS Ch.29.

Instructions

Compute Gochara (transit interpretation) for the seven grahas against a natal reference sign per BPHS Ch.29. Returns favourable/unfavourable verdict, house from natal, and raw vedha (obstruction) candidates per planet. The natal reference sign is the caller's choice — typically the natal Moon's sign (Chandra Gochara) or the natal Lagna's sign. Rahu and Ketu are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sunYesTransit sign index of Sun (0=Aries … 11=Pisces)
marsYesTransit sign index of Mars
moonYesTransit sign index of Moon
venusYesTransit sign index of Venus
saturnYesTransit sign index of Saturn
schoolNoExemption profile applied to the raw vedha candidate listGeometry
jupiterYesTransit sign index of Jupiter
mercuryYesTransit sign index of Mercury
vedha_tableNoVedha pair table sourceBphs29
natal_reference_signYesSign index of the natal reference point — natal Moon for Chandra Gochara, natal Lagna for Lagna-based Gochara

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv8.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "entries": {
+      "items": {
+        "properties": {
+          "classical_effect": {
+            "description": "Classical result attributed to this placement.",
+            "type": "string"
+          },
+          "graha": {
+            "description": "Transiting graha.",
+            "type": "string"
+          },
+          "house_from_natal": {
+            "description": "Count from the reference rashi, 1-12.",
+            "type": "integer"
+          },
+          "natal_reference_rashi": {
+            "description": "Rashi the count is taken from.",
+            "type": "integer"
+          },
+          "transit_rashi": {
+            "description": "Rashi the graha transits, 0=Aries … 11=Pisces.",
+            "type": "integer"
+          },
+          "vedha_candidates": {
+            "items": {
+              "description": "Graha whose placement would obstruct this effect.",
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "graha",
+          "transit_rashi",
+          "house_from_natal",
+          "classical_effect"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "entries"
+  ],
+  "type": "object"
+}
  2. First observedv7.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds useful behavioral context: the BPHS Ch.29 basis, the output items (favourable/unfavourable verdict, house from natal, raw vedha candidates), and the exclusion of Rahu/Ketu. There is no contradiction with the annotations.

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?

Three sentences with no filler: purpose, output, and usage context are each stated once and front-loaded. Every sentence earns its place.

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?

The description is sufficient for an agent to select and invoke the tool correctly given the rich schema and output schema. It supplies the missing domain context (BPHS Ch.29, seven grahas, natal reference choice, node exclusion) while the schema covers parameter mechanics and the output schema covers return structure.

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%, so the schema already documents all parameters including the two enums. The description's natal-reference guidance (Moon vs Lagna) largely duplicates the natal_reference_sign schema description. It adds minimal extra parameter meaning beyond what the schema already provides.

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?

The description uses a specific verb and resource: 'Compute Gochara (transit interpretation) for the seven grahas against a natal reference sign per BPHS Ch.29.' It also differentiates this tool from siblings like compute_transit by naming Gochara, the seven-planet scope, and the natal reference sign. The explicit exclusion of Rahu and Ketu further sharpens the tool's identity.

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 gives clear operational context: the caller chooses the natal reference sign, typically Moon (Chandra Gochara) or Lagna. It also states a when-not condition by saying Rahu and Ketu are not included. However, it never names a sibling alternative such as compute_transit or search_transits, so it stops short of fully 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