Skip to main content
Glama

Vastu Shastra MCP Server by RoxyAPI

by com.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
NameRequiredDescriptionDefault
langNoResponse 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
unitNoUnit 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
lengthYesLength 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.
breadthYesBreadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply.
compactNoSet 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.
ayadiTextNoWhich 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
perimeterNoPerimeter 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.
hastaInchesNoLength 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.
vyayaFormulaNoWhich 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
circumferenceNoCircumference 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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds meaningful behavioral context beyond that: it discloses that the three text families genuinely disagree, that every remainder is unit sensitive, and that feet/metres are converted using hastaInches and rounded to whole cubits. It also states that the response shows remainders, member names, and two verdict rules, and that utpala falls back to the perimeter family. This is rich behavioral disclosure that helps an agent predict output shape and edge cases.

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 two sentences: the first states the core function and return contents, the second gives selection guidance for text families and cubit length. Every clause earns its place, and the most decision-relevant information (text families disagree, unit sensitivity) is front-loaded. It is detailed without being bloated, and it does not repeat schema content verbatim.

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?

For a 10-parameter calculator with no output schema, this description is remarkably complete. It tells the agent what inputs matter, why they matter, what the output will contain (all six formulas, multiplier, divisor, remainder, member names, two verdict rules), and how to choose among the natural options. The absence of an output schema is mitigated by the description's explicit statement of return contents. There is no obvious missing context that would prevent correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is already 3, and the schema descriptions are unusually thorough: they explain which formulas each parameter feeds, default conventions, unit conversion behavior, and ignored cases. The tool description adds additional semantic context by highlighting unit sensitivity and the fact that the three text families disagree, which helps an agent understand why parameters like ayadiText and hastaInches matter. Minor deduction because the description itself doesn't enumerate parameters, but the schema already carries that weight, so a 4 is fair.

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 and resource: 'Ayadi shadvarga calculator for a building or a room: send the dimensions and the API returns all six proportional formulas.' It also distinguishes this tool from the sibling vastu tools by focusing on Ayadi proportions, yoni, and shadvarga rather than devatas, directions, entrances, mandalas, plots, rooms, or timing. It is unambiguous about what the tool computes and for whom.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: for practitioner tools, plan checking software, and anyone justifying a dimension. It includes a clear decision about choosing among three text families because they genuinely disagree, and choosing a cubit length because remainders are unit sensitive. It names two alternatives (ayadiText families, perimeter vs. Manasara) and explains when each is appropriate. This is far beyond a typical vague 'use this for Ayadi calculations' and gives an agent actionable routing.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource or analytical step: reference lookups (devatas, directions) are cleanly separated from computations (ayadi, entrance, mandala, plot, rooms, timing), and the list endpoints are distinguished from their _id counterparts by an explicit suffix. Although three post_ tools accept plot geometry, their outputs are mutually exclusive (grid overlay vs. property verdict vs. room-by-room check), and the descriptions state each purpose with enough precision to prevent misselection.

Naming Consistency5/5

All ten tools follow a uniform lowercase snake_case pattern with a get_ or post_ prefix and the vastu domain token consistently in second position. The get_ prefix is reserved for read-only reference data while post_ marks computational endpoints, and the _id suffix uniformly marks single-item lookups, creating a highly predictable scheme.

Tool Count5/5

Ten tools is a well-scoped count for a domain-specific server covering reference data, analysis, and timing. Each tool earns its place: the two list/detail pairs follow standard API practice without redundancy, and the six computational tools each address a distinct stage of Vastu analysis.

Completeness4/5

The tool surface covers the full Vastu consulting workflow: reference data (devatas, directions), land assessment (plot), grid projection (mandala), entrance validation, room placement, dimensional proportion checks (ayadi), and housewarming date selection (griha pravesh). The only notable gap is that timing is restricted to griha pravesh, leaving other Vastu-related muhurta events like construction commencement uncovered.

Resources