Skip to main content
Glama

Vastu Shastra MCP Server by RoxyAPI

by com.roxyapi

Calculate entrance pada - Vastu main door direction API

post_vastu_entrance
Read-only

Vastu entrance analysis for a main door: send the plot and where the door sits, and the API returns which of the 32 perimeter padas it falls on, the devata of that square, the effect the classical chapter gives that pada, and the favourable padas on the same side to move toward. Every verdict carries the chapter and verse it comes from as a typed field, and the reading holds on either the 81 pada or the 64 pada division. Built for property and interior design tools, practitioner reports, and any product that has to say whether a front door is well placed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doorNoWhere the main door sits, in plot coordinates. The point is snapped to the nearest boundary of the plot, so a coordinate read off a drawing that lands slightly inside or outside still resolves. Send this or doorPosition, never both.
gridNoWhich division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.81-pada
langNoResponse 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
plotYesThe ground the mandala is projected over. Send width and depth for a compass-aligned rectangle, or polygon for anything else. The x axis runs east and the y axis north, and the mandala is aligned to the compass rather than to the building.
facingNoDirection the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.
compactNoSet 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.
doorPositionNoWhere the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.
facingDegreesNoDirection the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.

Schema Changelog

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

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive, so safety is covered. The description adds meaningful behavioral context: verdicts carry chapter and verse as typed fields, the analysis works on both the 81-pada and 64-pada grids, and the result includes favourable padas to move toward. This goes beyond what the schema or annotations alone state.

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, front-loaded with the core function and return value, followed by the scholarly sourcing guarantee and target use cases. Every sentence earns its place and adds a distinct piece of information without padding.

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?

For a complex domain tool with no output schema, the description covers the essential outputs, the supported grid systems, the sourcing of verdicts, and the intended use cases. It does not enumerate response field names, but it gives enough conceptual detail for an agent to select and invoke the tool correctly with the schema filling in the rest.

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%, and the schema already explains every parameter in detail, including coordinate conventions, units, exclusivity rules, and defaults. The tool description adds little parameter-level meaning, which is acceptable because the schema carries the full burden.

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: it analyzes a main door and returns the 32-pada it falls on, its devata, the classical effect, and favourable alternative padas. This clearly separates it from sibling Vastu tools, which cover devatas, directions, mandalas, and rooms rather than entrance pada analysis.

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 application context: property tools, interior design products, practitioner reports, and any product that must judge whether a front door is well placed. It does not explicitly contrast this tool with siblings such as post_vastu_rooms or get_vastu_directions, so it stops short of a full when-not-to-use statement.

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 toolsInspect
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