Vastu Shastra MCP Server by RoxyAPI

List the 45 devatas - Vastu Purusha Mandala reference API

get_vastu_devatas

Read-only

Reference table of the 45 devatas of the Vastu Purusha Mandala: which squares of the 81 pada grid each one holds, which ring and which side, how many padas, and the verses that place it. A pure reference endpoint with no plot required, for building a mandala diagram or a glossary. Where the sources contradict each other, and they do on several rows, the row says so instead of quietly picking a side.

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
`limit`	No	Maximum items to return per page. Range: 1-45, default 45.
`offset`	No	Number of items to skip for pagination. Default 0.
`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
`limit`	Yes
`total`	Yes
`offset`	Yes
`devatas`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "devatas": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "devatas"
+  ],
+  "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 declare readOnlyHint=true, and the description reinforces a safe read-only reference behavior with 'pure reference endpoint. It adds valuable behavioral context beyond annotations by explaining that contradictory sources are disclosed in the rows instead of being silently resolved.

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 sentences with no waste: the first states the resource and fields, the second gives the use case and the non-plot constraint, and the third discloses contradiction behavior. Each sentence earns its place and the key scoping detail 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?

The description, combined with full schema documentation, read-only annotations, and an output schema, gives an agent everything needed to select and invoke the tool correctly. It explains content depth, the no-plot requirement, and even edge-case handling around source contradictions.

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%, with detailed descriptions for lang, limit, offset, and compact, so the schema carries the parameter semantics. The description does not add meaning about how parameters behave, but given full schema coverage, the baseline 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 names a specific resource (the 45 devatas of the Vastu Purusha Mandala) and states precisely what is included: grid squares, ring, side, pada count, and verses. It also differentiates the tool from plotting-related siblings by calling it a 'pure reference endpoint with no plot required.'

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 gives clear use cases: 'for building a mandala diagram or a glossary' and a clear exclusion: 'no plot required. It does not explicitly name alternative sibling tools such as get_vastu_devatas_id for single-record lookups, but the context is strong enough for an agent to choose this tool correctly.

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?