Vastu Shastra MCP Server by RoxyAPI

Look up one direction - Vastu dikpala reference API

get_vastu_directions_id

Read-only

Look up one Vastu direction: its dikpala, the mandala squares it covers with their devatas, what the chapter places there, and what standing water in that quarter brings. Case and punctuation in the id are folded, so north-east, northeast and NorthEast all resolve to the same entry, and the id space is the one the feng shui and I Ching endpoints use.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Direction id, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. 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
`kind`	Yes
`water`	Yes
`places`	No
`devatas`	Yes
`dikpala`	Yes
`element`	No
`sources`	Yes
`squares`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond those annotations: case and punctuation folding in the id, and the fact that this id space is shared with other endpoints. This enriches the agent's understanding without contradicting 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 two sentences with no filler. It front-loads the primary action and output content, then provides the normalization and cross-API context in the second sentence. Every clause earns 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?

For a read-only single-direction lookup with an output schema and three fully documented parameters, the description is complete. It covers what the tool returns, mentions id normalization behavior, and situates the id in a shared endpoint ecosystem. The lang and compact parameters are fully handled by the schema, so nothing essential is missing.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining that id normalization applies to case and punctuation and that the id space is the same one used by feng shui and I Ching endpoints, which is a meaningful semantic addition for cross-tool use. The other parameters are already fully described in the schema.

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 uses a specific verb and resource: 'Look up one Vastu direction' and then enumerates the rich output fields (dikpala, mandala squares and devatas, chapter placement, standing water meaning). It clearly distinguishes itself from the sibling list tool get_vastu_directions by saying 'one' direction, and the id-sharing note ties it into a broader endpoint family.

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 phrase 'Look up one Vastu direction' makes the primary use case obvious)Skip versus get_vastu_directions. It also explains that the id space is shared with feng shui and I Ching endpoints, guiding use across related APIs. It stops short of explicitly naming alternatives or saying when not to use it, but the context is clear enough.

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?