Vastu Shastra MCP Server by RoxyAPI

Find griha pravesh dates - Vastu house warming muhurta API

post_vastu_timing_griha_pravesh

Read-only

Griha pravesh muhurta search over a date window: send the window and the place, and the API returns every day that clears the classical day-level rules, with the nakshatra, tithi, weekday and solar position that qualified it and the rule ids that admitted it. Two Muhurta texts disagree on the admissible nakshatras and you choose which one leads, and the rules a date search cannot settle are published rather than dropped. Built for house warming date pickers, practitioner scheduling and agent assistants that have to answer when a family should move in.

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
`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.
`endDate`	Yes	Last day of the search window, in YYYY-MM-DD, inclusive. The window is capped at 93 days, which is a full season and the same cap the Vedic auspicious day search carries.
`latitude`	Yes	Latitude of the house, in decimal degrees, positive north. Sunrise decides where one day ends and the next begins, so a nakshatra running out during the morning changes which day it counts for.
`timezone`	Yes	IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.
`longitude`	Yes	Longitude of the house, in decimal degrees, positive east.
`startDate`	Yes	First day of the search window, in YYYY-MM-DD. Every limb is read at sunrise of the local day, because the Hindu day begins at sunrise rather than at midnight.
`muhurtaText`	No	Which Muhurta text supplies the admissible nakshatras for entering a new house. muhurta-chintamani admits eight and kalaprakasika admits twelve; seven overlap and are the high confidence core, one is unique to the first and five to the second. The two texts are independent witnesses, which is what makes the overlap strong and the difference worth exposing. Defaults to muhurta-chintamani.	muhurta-chintamani

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	Yes
`rules`	Yes
`total`	Yes
`window`	Yes
`sources`	Yes
`conventions`	Yes
`rejectionsByRule`	Yes
`leftToTheAstrologer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "muhurtaText": {
+          "type": "string"
+        },
+        "timezone": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "muhurtaText",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    "days": {
+      "items": {
+        "properties": {
+          "admittedBy": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "ayana": {
+            "type": "string"
+          },
+          "date": {
+            "type": "string"
+          },
+          "karana": {
+            "type": "string"
+          },
+          "nakshatra": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "number",
+              "id",
+              "name"
+            ],
+            "type": "object"
+          },
+          "quality": {
+            "type": "string"
+          },
+          "reading": {
+            "type": "string"
+          },
+          "solarLongitude": {
+            "type": "number"
+          },
+          "sunrise": {
+            "type": "string"
+          },
+          "tithi": {
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              },
+              "paksha": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "number",
+              "name",
+              "paksha"
+            ],
+            "type": "object"
+          },
+          "vara": {
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "number",
+              "name"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "date",
+          "nakshatra",
+          "tithi",
+          "vara",
+          "ayana",
+          "solarLongitude",
+          "karana",
+          "quality",
+          "admittedBy",
+          "reading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "leftToTheAstrologer": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rejectionsByRule": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "type": "object"
+    },
+    "rules": {
+      "items": {
+        "properties": {
+          "confidence": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "requirement": {
+            "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"
+          }
+        },
+        "required": [
+          "id",
+          "requirement",
+          "confidence",
+          "source"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "total": {
+      "type": "number"
+    },
+    "window": {
+      "properties": {
+        "daysEvaluated": {
+          "type": "number"
+        },
+        "endDate": {
+          "type": "string"
+        },
+        "startDate": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "startDate",
+        "endDate",
+        "daysEvaluated"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "days",
+    "total",
+    "window",
+    "rejectionsByRule",
+    "rules",
+    "leftToTheAstrologer",
+    "sources",
+    "conventions"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / timezone / description

Previous value: -"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."

First observedSep 6, 2026

TDQS

A4.3/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 description's emphasis on returning data without mutation aligns. It adds substantial behavioral context beyond the annotations: the API exposes disagreement between two Muhurta texts (muhurta-chintamani vs kalaprakasika) and the user chooses which leads, and it 'publishes rather than drops' rules a date search cannot settle. This gives an agent a clear model of the tool's decision logic and output philosophy.

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?

The description is three sentences, each earning its place: the first defines the search and its outputs, the second explains the text-disagreement and rule-handling behavior, and the third lists use cases. It is front-loaded with the core purpose and avoids redundancy. Slightly verbose but not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown but known to exist) and the richly described input schema (100% coverage), the description provides a complete high-level overview. It mentions the return fields, the text-selection mechanism, and the rule-publishing behavior. It does not mention the 93-day window cap or the exact rule lists, but those are in the schema, so the agent can find them. For a tool with 8 parameters and 5 required, this is adequately complete.

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 every parameter is already documented in detail (e.g., timezone has a full explanation of IANA vs fixed offsets, latitude explains sunrise-based day boundaries). The tool description itself adds no parameter-specific semantics beyond the high-level mention of 'date window' and 'place,' which the schema already conveys. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states it is a 'Griha pravesh muhurta search over a date window' and explains what it returns: days clearing classical rules with nakshatra, tithi, weekday, solar position, and rule IDs. This distinguishes it from siblings (devatas, directions, ayadi, entrance, etc.), which are unrelated to date search.

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 names its intended use cases: 'house warming date pickers, practitioner scheduling and agent assistants that have to answer when a family should move in.' It does not explicitly say when not to use it, but the sibling tools are topically distinct, making the appropriate context clear. The phrase 'search over a date window' implies a query for eligible dates rather than a single-date calculation.

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?