Skip to main content
Glama
arthiqlabs

Vedaksha

by arthiqlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

compute_bhavas

Read-only

Calculate the Vedic whole-sign bhava chart from an ascendant longitude, returning house classifications and planets' house placements.

Instructions

Compute the whole-sign bhava (house) chart from an ascendant. In the Vedic whole-sign system the entire sign containing the ascendant is the 1st bhava, the next sign the 2nd, and so on — houses do not have cusps within signs. Returns the sign of each of the twelve bhavas with its kendra / trikona / dusthana / upachaya classification, and optionally places supplied grahas into their bhavas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planetsNoOptional map of graha name to sidereal longitude, e.g. {"Mars": 200.4}. Each is placed into its bhava.
ascendantYesSidereal longitude of the ascendant [0, 360)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
housesYesTwelve entries in order.
planetsNoEmpty unless grahas were supplied.
lagna_signYesRashi of the ascendant, 0=Aries … 11=Pisces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv8.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "houses": {
+      "description": "Twelve entries in order.",
+      "items": {
+        "properties": {
+          "bhava": {
+            "description": "House number, 1-12.",
+            "type": "integer"
+          },
+          "is_dusthana": {
+            "description": "True for houses 6, 8, 12.",
+            "type": "boolean"
+          },
+          "is_kendra": {
+            "description": "True for houses 1, 4, 7, 10.",
+            "type": "boolean"
+          },
+          "is_trikona": {
+            "description": "True for houses 1, 5, 9.",
+            "type": "boolean"
+          },
+          "is_upachaya": {
+            "description": "True for houses 3, 6, 10, 11.",
+            "type": "boolean"
+          },
+          "sign": {
+            "description": "Rashi occupying it, 0=Aries … 11=Pisces.",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "bhava",
+          "sign"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lagna_sign": {
+      "description": "Rashi of the ascendant, 0=Aries … 11=Pisces.",
+      "type": "integer"
+    },
+    "planets": {
+      "description": "Empty unless grahas were supplied.",
+      "items": {
+        "properties": {
+          "bhava": {
+            "description": "House the graha falls in, 1-12.",
+            "type": "integer"
+          },
+          "longitude": {
+            "description": "Sidereal longitude in degrees [0, 360).",
+            "type": "number"
+          },
+          "planet": {
+            "description": "Graha name as supplied.",
+            "type": "string"
+          },
+          "sign": {
+            "description": "Rashi it occupies, 0=Aries … 11=Pisces.",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "planet",
+          "bhava"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "lagna_sign",
+    "houses"
+  ],
+  "type": "object"
+}
  2. First observedv7.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With only readOnlyHint available, the description carries the burden of explaining the computation's behavioral traits. It does this well by describing the whole-sign rule, the classification output, and optional graha placement. There is no contradiction with the read-only annotation.

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?

Two dense sentences deliver the core purpose, the computational rule, the return contents, and the optional planet behavior. There is no filler, and the main verb is front-loaded.

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 small parameter count, the presence of an output schema, and the read-only annotation, the description is fully sufficient for correct invocation. It covers inputs, computation rule, returned data, and optional behavior without leaving important gaps.

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 both parameters are already well documented in the schema. The tool description adds little beyond restating sidereal longitude and the optional planet map, so it meets the baseline but does not substantially exceed 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 the whole-sign bhava (house) chart from an ascendant.' It also differentiates the tool from cusp-based systems by stating that 'houses do not have cusps within signs,' making the purpose unmistakable.

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?

The description implies when to use the tool: whenever a whole-sign bhava chart is needed from an ascendant. However, it does not explicitly name sibling alternatives like compute_natal_chart or compute_vargas, nor does it state when this tool should not be used. The context is clear but the exclusion guidance is missing.

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