Skip to main content
Glama
arthiqlabs

Vedaksha

by arthiqlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

compute_ashtakavarga

Read-only

Calculates Bhinna Ashtakavarga raw bindu tables and Sarvashtakavarga for all seven planets using sign positions, enabling Vedic astrology strength analysis from BPHS Chapter 66.

Instructions

Compute Bhinna Ashtakavarga (raw bindu tables) and Sarvashtakavarga for all 7 planets from sign positions. Source: BPHS Ch.66 vv.13-68. Trikona/Ekadhipatya Shodhana and Pinda Sadhana are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sunYesSign index of Sun (0=Aries…11=Pisces)
marsYesSign index of Mars (0=Aries…11=Pisces)
moonYesSign index of Moon (0=Aries…11=Pisces)
lagnaYesSign index of Lagna (Ascendant)
venusYesSign index of Venus (0=Aries…11=Pisces)
saturnYesSign index of Saturn (0=Aries…11=Pisces)
jupiterYesSign index of Jupiter (0=Aries…11=Pisces)
mercuryYesSign index of Mercury (0=Aries…11=Pisces)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tablesYesOne Bhinna Ashtakavarga per graha.
sarvashtakavargaYesTwelve entries, Aries first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv8.0.0
    • addedInput schema / properties / jupiter / description
      Added value: +"Sign index of Jupiter (0=Aries…11=Pisces)"
    • addedInput schema / properties / mars / description
      Added value: +"Sign index of Mars (0=Aries…11=Pisces)"
    • addedInput schema / properties / mercury / description
      Added value: +"Sign index of Mercury (0=Aries…11=Pisces)"
    • addedInput schema / properties / moon / description
      Added value: +"Sign index of Moon (0=Aries…11=Pisces)"
    • addedInput schema / properties / saturn / description
      Added value: +"Sign index of Saturn (0=Aries…11=Pisces)"
    • addedInput schema / properties / venus / description
      Added value: +"Sign index of Venus (0=Aries…11=Pisces)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "sarvashtakavarga": {
+      "description": "Twelve entries, Aries first.",
+      "items": {
+        "description": "Summed bindus in one rashi.",
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "tables": {
+      "description": "One Bhinna Ashtakavarga per graha.",
+      "items": {
+        "properties": {
+          "bindus": {
+            "description": "Twelve entries, Aries first.",
+            "items": {
+              "description": "Bindus in one rashi, 0-8.",
+              "type": "integer"
+            },
+            "type": "array"
+          },
+          "planet": {
+            "description": "Graha whose Bhinna Ashtakavarga this is.",
+            "type": "string"
+          },
+          "total": {
+            "description": "Sum of this graha's bindus.",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "planet",
+          "bindus",
+          "total"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "tables",
+    "sarvashtakavarga"
+  ],
+  "type": "object"
+}
  2. First observedv7.0.0

TDQS

A3.8/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, so the safety profile is covered. The description adds useful behavioral context by specifying the source (BPHS Ch.66 vv.13-68) and explicitly stating that Trikona/Ekadhipatya Shodhana and Pinda Sadhana are not included, which sets accurate expectations for the output. No contradiction with 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 short sentences with no filler: the main function is stated first, the source is given second, and the important exclusions are last. Every sentence contributes meaningful information.

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

Completeness4/5

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

The tool is read-only, has an output schema, and all 8 required input parameters are fully documented. The description covers the core computation, scope, and limitations. The only minor ambiguity is the relationship between 'all 7 planets' and the required lagna parameter, which is not fully explained, but this is a small gap given the otherwise strong structured metadata.

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 already has a clear meaning: sign index with 0=Aries through 11=Pisces. The description reinforces the 'sign positions' basis but adds no new parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific verb ('Compute'), a specific resource ('Bhinna Ashtakavarga' raw bindu tables and 'Sarvashtakavarga'), and the input basis ('from sign positions'). It is clearly distinguishable from the sibling compute_* tools by naming a unique astrological domain and clarifying what is not included.

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?

The description gives no explicit guidance about when to use this tool versus alternatives like compute_shadbala, compute_dasha, or compute_gochara. The exclusions tell the agent what the computation does not include, but they do not help an agent decide when this tool is the right choice.

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