Vastu Shastra MCP Server by RoxyAPI

Calculate Ayadi shadvarga - Vastu proportion and yoni calculator API

post_vastu_ayadi

Read-only

Ayadi shadvarga calculator for a building or a room: send the dimensions and the API returns all six proportional formulas with the multiplier, the divisor and the remainder shown, the member each remainder names, and the two verdict rules the texts state. Choose between three text families, which genuinely disagree, and choose your own cubit length, because every remainder is unit sensitive. Built for practitioner tools, plan checking software and anyone who has to justify a dimension rather than assert it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`unit`	No	Unit the Ayadi dimensions are given in. Every remainder is unit sensitive, so this is an input and never assumed: the same building measured in cubits and in feet gives different remainders. hasta is the classical cubit and needs no conversion; feet and metres are converted using hastaInches and rounded to whole cubits, and the rounded figures are returned. Defaults to hasta.	hasta
`length`	Yes	Length of the building or room, in the unit given. Under the Manasara family this is the measure the aya and rksha formulas multiply; under the perimeter family it only feeds the perimeter.
`breadth`	Yes	Breadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply.
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`ayadiText`	No	Which family of Ayadi formulas to apply. manasara takes length, breadth and circumference separately and is double sourced. perimeter-texts runs every formula on the perimeter alone and is the family the usual worked example is printed for. utpala supplies a yoni formula from the length times the breadth and nothing else, so the other five vargas fall back to the perimeter family and the response says so. Defaults to manasara.	manasara
`perimeter`	No	Perimeter of the plan, if it is not simply twice the length plus twice the breadth. The perimeter family runs every formula on this one measure, so it is the number that decides all six remainders there.
`hastaInches`	No	Length of one hasta, the classical cubit, in inches. Defaults to 18, which is 24 angula at three quarters of an inch each and is the value three independent sources agree on. Raise it if your lineage measures the cubit differently; the value used is echoed on the response so a stored reading can be reproduced years later. Only used when unit is feet or metres.
`vyayaFormula`	No	Which vyaya formula the perimeter family uses. The printed table gives two joined by the word or and states no rule for choosing. p9-10 multiplies by nine and divides by ten, which is the only divisor consistent with the ten member vyaya group, so its remainder can be placed in that group and it is the default. p3-14 multiplies by three and divides by fourteen, and its remainder maps to no group any source enumerates. Ignored when ayadiText is manasara, which has one vyaya formula.	p9-10
`circumference`	No	Circumference or height, if the Manasara vara and tithi formulas should read something other than the perimeter. Defaults to the perimeter, which is what a rectangular plan supplies.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`vayas`	Yes
`vargas`	Yes
`verdict`	Yes
`measures`	Yes
`conventions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "ayadiText": {
+          "type": "string"
+        },
+        "hastaInches": {
+          "type": "number"
+        },
+        "unit": {
+          "type": "string"
+        },
+        "vyayaFormula": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "ayadiText",
+        "vyayaFormula",
+        "unit",
+        "hastaInches"
+      ],
+      "type": "object"
+    },
+    "measures": {
+      "properties": {
+        "area": {
+          "type": "number"
+        },
+        "breadth": {
+          "type": "number"
+        },
+        "circumference": {
+          "type": "number"
+        },
+        "length": {
+          "type": "number"
+        },
+        "perimeter": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "length",
+        "breadth",
+        "perimeter",
+        "circumference",
+        "area"
+      ],
+      "type": "object"
+    },
+    "vargas": {
+      "items": {
+        "properties": {
+          "auspicious": {
+            "type": "boolean"
+          },
+          "divisor": {
+            "type": "number"
+          },
+          "firstName": {
+            "type": "string"
+          },
+          "gloss": {
+            "type": "string"
+          },
+          "groupSize": {
+            "type": "number"
+          },
+          "multiplier": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "operand": {
+            "type": "string"
+          },
+          "operandValue": {
+            "type": "number"
+          },
+          "product": {
+            "type": "number"
+          },
+          "remainder": {
+            "type": "number"
+          },
+          "source": {
+            "properties": {
+              "basis": {
+                "type": "string"
+              },
+              "chapter": {
+                "type": "number"
+              },
+              "publicDomain": {
+                "type": "boolean"
+              },
+              "text": {
+                "type": "string"
+              },
+              "translation": {
+                "type": "string"
+              },
+              "verse": {
+                "type": "string"
+              },
+              "year": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "text"
+            ],
+            "type": "object"
+          },
+          "varga": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "varga",
+          "operand",
+          "operandValue",
+          "multiplier",
+          "divisor",
+          "product",
+          "remainder",
+          "groupSize",
+          "source"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "vayas": {
+      "type": "number"
+    },
+    "verdict": {
+      "properties": {
+        "ayaVyaya": {
+          "type": "string"
+        },
+        "reading": {
+          "type": "string"
+        },
+        "source": {
+          "properties": {
+            "basis": {
+              "type": "string"
+            },
+            "chapter": {
+              "type": "number"
+            },
+            "publicDomain": {
+              "type": "boolean"
+            },
+            "text": {
+              "type": "string"
+            },
+            "translation": {
+              "type": "string"
+            },
+            "verse": {
+              "type": "string"
+            },
+            "year": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "text"
+          ],
+          "type": "object"
+        },
+        "yoniAuspicious": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "yoniAuspicious",
+        "ayaVyaya",
+        "reading",
+        "source"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "measures",
+    "vargas",
+    "vayas",
+    "verdict",
+    "conventions"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With readOnlyHint=true and destructiveHint=false, the safety profile is already covered by annotations, and the description adds rich behavioral context: six formulas with multiplier, divisor, remainder, member names, two verdict rules, family disagreements, unit-sensitive remainders, and conversion behavior to whole cubits for feet/metres. It also mentions the compact output shape, which is beyond 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?

The description is three tight sentences with no filler. It front-loads the result an agent can expect, then gives the key choices and the intended use case, making every sentence earn 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?

Given that an output schema exists and all 10 parameters are fully documented in the input schema, the description covers the remaining context: what the tool calculates, why the text families matter, unit-sensitivity, and who should use it. Nothing critical for selecting or invoking the tool is missing.

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?

The schema describes every parameter at 100% coverage, so the baseline is 3. The description reinforces the conceptual model behind unit, ayadiText, and hastaInches, but it does not add significant parameter-level 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 opens with a specific verb ('returns') and resource ('all six proportional formulas') and immediately names the domain as an 'Ayadi shadvarga calculator for a building or a room'. It clearly distinguishes the tool from the Vastu sibling tools by describing the exact computation and judgment output rather than restating the title.

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?

The description states the intended contexts: practitioner tools, plan checking software, and anyone who has to justify a dimension. It explains the key choice between three text families and the unit-sensitivity caveat, but it does not explicitly name when not to use it or compare it to sibling tools; the distinct sibling names make the target use unambiguous.

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

All Vastu Shastra MCP Server by RoxyAPI 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.

Resources

Need Help?