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 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.
`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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false in annotations, the description adds genuinely useful behavioral context beyond them: the two Muhurta texts disagree and the caller chooses which leads, and 'the rules a date search cannot settle are published rather than dropped.' These are non-obvious behaviors an agent needs to know. No contradiction with annotations.

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, each earning its place: the first front-loads the core operation and output shape, the second explains the muhurtaText behavioral quirk, and the third states the audience. The first sentence is dense but information-packed rather than padded.

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?

Despite having no output schema, the description compensates by spelling out the return contents (nakshatra, tithi, weekday, solar position, rule ids). Together with fully documented parameters and a clear use case, an agent has what it needs to invoke the tool correctly. Minor gaps remain: no statement about the empty-result case or error behavior beyond the timezone 400 note in the schema.

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 of 3 applies — the schema already documents all 8 parameters in detail, including the muhurta-chintamani vs kalaprakasika divergence (8 vs 12 nakshatras, 7 overlap). The description adds only the high-level 'send the window and the place' framing, which is helpful but not substantial beyond 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 names a specific verb and resource — 'Griha pravesh muhurta search over a date window' — and enumerates exactly what is returned (qualified days with nakshatra, tithi, weekday, solar position, rule ids). The tool's timing/muhurta focus clearly sets it apart from sibling tools about devatas, directions, ayadi, mandala, plot, entrance, and rooms.

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 closing sentence gives explicit use contexts: 'Built for house warming date pickers, practitioner scheduling and agent assistants that have to answer when a family should move in.' This is clear when-to-use guidance, though it stops short of naming alternatives or stating when-not-to-use conditions relative to the sibling vastu tools.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct resource or analytical step: reference lookups (devatas, directions) are cleanly separated from computations (ayadi, entrance, mandala, plot, rooms, timing), and the list endpoints are distinguished from their _id counterparts by an explicit suffix. Although three post_ tools accept plot geometry, their outputs are mutually exclusive (grid overlay vs. property verdict vs. room-by-room check), and the descriptions state each purpose with enough precision to prevent misselection.

Naming Consistency5/5

All ten tools follow a uniform lowercase snake_case pattern with a get_ or post_ prefix and the vastu domain token consistently in second position. The get_ prefix is reserved for read-only reference data while post_ marks computational endpoints, and the _id suffix uniformly marks single-item lookups, creating a highly predictable scheme.

Tool Count5/5

Ten tools is a well-scoped count for a domain-specific server covering reference data, analysis, and timing. Each tool earns its place: the two list/detail pairs follow standard API practice without redundancy, and the six computational tools each address a distinct stage of Vastu analysis.

Completeness4/5

The tool surface covers the full Vastu consulting workflow: reference data (devatas, directions), land assessment (plot), grid projection (mandala), entrance validation, room placement, dimensional proportion checks (ayadi), and housewarming date selection (griha pravesh). The only notable gap is that timing is restricted to griha pravesh, leaving other Vastu-related muhurta events like construction commencement uncovered.

Resources

Need Help?