Vastu Shastra MCP Server by RoxyAPI

Look up one devata - Vastu mandala devata reference API

get_vastu_devatas_id

Read-only

Look up one devata of the Vastu Purusha Mandala: the squares it holds, its ring and side, its pada count, the entrance pada it governs where it sits on the perimeter, and the verses that place it. Case and punctuation in the id are folded, so indra-outer, Indra_Outer and INDRA OUTER all resolve.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Devata id, lower case transliteration. The two Indras are indra-outer for the east perimeter square and indra-inner for the inner ring one. Case and punctuation are folded.
`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
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`note`	No
`role`	Yes
`side`	No
`cells`	Yes
`class`	Yes
`group`	No
`source`	Yes
`verses`	Yes
`squares`	Yes
`quadrant`	No
`padaCount`	Yes
`entrancePada`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cells": {
+      "items": {
+        "properties": {
+          "columnFromWest": {
+            "type": "number"
+          },
+          "rowFromNorth": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "rowFromNorth",
+          "columnFromWest"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "class": {
+      "enum": [
+        "perimeter",
+        "innerRing",
+        "innerCorner",
+        "center"
+      ],
+      "type": "string"
+    },
+    "entrancePada": {
+      "type": "number"
+    },
+    "group": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "padaCount": {
+      "type": "number"
+    },
+    "quadrant": {
+      "type": "string"
+    },
+    "role": {
+      "type": "string"
+    },
+    "side": {
+      "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"
+    },
+    "squares": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "verses": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "class",
+    "squares",
+    "cells",
+    "padaCount",
+    "role",
+    "verses",
+    "source"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already signal readOnlyHint and non-destructive behavior. The description adds genuinely useful behavioral context: id case/punctuation folding ('indra-outer, Indra_Outer and INDRA OUTER all resolve') and the specific semantic fields returned. It does not discuss error behavior, but the schema enum and read-only annotation reduce that burden.

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 compact, front-loaded, and information-dense. The first clause states the action and resource, the field list specifies the return scope, and the second sentence covers id normalization with concrete examples. No sentence is wasted.

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 read-only annotations, a fully described input schema, and an output schema, the description provides everything needed to invoke the tool correctly: what it returns, how id matching works, and how it differs from sibling lookups. Nothing essential 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?

Schema description coverage is 100%, so the baseline is 3. The description reinforces the id folding behavior already stated in the schema but adds no new parameter-level meaning; lang and compact behavior are left entirely to the schema. This is acceptable but not additive.

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: 'Look up one devata of the Vastu Purusha Mandala.' It then enumerates exactly what data is returned, which clearly distinguishes this single-item lookup from the plural-list sibling get_vastu_devatas and from direction lookups.

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 'one devata' phrasing makes the single-record context clear, and the sibling list reinforces the distinction from get_vastu_devatas. However, it does not explicitly state 'use this instead of get_vastu_devatas when you need one id' or mention exclusions, so it stops short of a 5.

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?