Vastu Shastra MCP Server by RoxyAPI

List the eight directions - Vastu dikpala and direction reference API

get_vastu_directions

Read-only

Reference table of the eight Vastu directions: the dikpala who rules each quarter of the horizon, the squares of the mandala it covers with their devatas, what the chapter places on that side, and what standing water there brings. A pure reference endpoint with no plot required, for building a picker or a directions guide. Every row says which verse each part comes from and labels the element as the later convention it is.

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-8, default 8.
`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
`directions`	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": {
+    "directions": {
+      "items": {
+        "properties": {
+          "devatas": {
+            "items": {
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "square": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "square",
+                "id",
+                "name"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "dikpala": {
+            "type": "string"
+          },
+          "element": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "places": {
+            "type": "string"
+          },
+          "sources": {
+            "items": {
+              "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"
+            },
+            "type": "array"
+          },
+          "squares": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          },
+          "water": {
+            "properties": {
+              "auspiciousness": {
+                "type": "string"
+              },
+              "effect": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "effect",
+              "auspiciousness"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "id",
+          "dikpala",
+          "kind",
+          "squares",
+          "devatas",
+          "water",
+          "sources"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "directions"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces this with 'pure reference endpoint' and adds useful behavioral detail: every row cites its source verse and labels the element as the later convention. This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: the first packs the content list, the second gives the use case, and the third explains row provenance. There is no filler, though 'reference' appears twice; overall it is efficient and 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?

For a simple list endpoint with full schema coverage and an output schema, the description covers purpose, content, use case, and a key behavioral distinction (no plot required). Everything an agent needs to call it correctly is present.

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 lang, limit, offset, and compact each fully described. The description adds no parameter-specific detail, so it appropriately relies on the schema; baseline 3 applies.

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 explicitly states 'Reference table of the eight Vastu directions' and enumerates the row contents (dikpala, devatas, chapter placements, standing water). The title 'List the eight directions' and the listing behavior clearly distinguish it from get_vastu_directions_id and get_vastu_devatas.

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?

It gives clear context: 'A pure reference endpoint with no plot required, for building a picker or a directions guide.' This implies it is for read-only reference rather than plot/post endpoints, though it does not explicitly name alternatives or state when not to use it.

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?