Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

The 8, 16 or 32 zones

astroway_vastu_shastra_vastu_zones
Read-onlyIdempotent

Splits a Vastu plan into 8, 16 or 32 compass zones with exact bounds, mapping each room and fixture to its sector so you can judge placement and directional readings.

Instructions

The compass split into 8, 16 or 32 centred sectors with exact bounds. For 16, each zone carries its room from Muhurta Chintamani 12.21, a short reading in our own words, elements and colours as sourced variants (writers disagree), and a guardian and planet only where a source names one. Send a plan in the /vastu/plan format and each zone lists the rooms and fixtures that fall in it, read from the area centre or the grid centre.

[Group: Vastu Shastra] [Endpoint: POST /v1/vastu/zones] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_vastu_shastra_vastu_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
roomsNo
centreNo
coordsNo
facingNo
schoolNo
boundaryNo
entranceNo
northAngleNo
declinationNo
granularityNo
scoreVersionNo
entranceMethodNo
northReferenceNo

Output Schema

NameRequiredDescriptionDefault
fromNo
notesNo
orderNo
zonesNo
warningsNo
granularityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful domain behavior: source attribution (Muhurta Chintamani), handling of disagreements between sources, conditional inclusion of guardians/planets, and that room/fixture assignment can be read from area or grid centre. It does not discuss rate limits or output format, but the output schema covers that.

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 front-loaded with the core concept and then adds detail. It is dense but not wasteful; the long second sentence about 16-zone contents is informative. The bracketed metadata is kept separate.

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

Completeness3/5

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

For a complex tool with 14 parameters, nested objects, and no parameter descriptions, the description is incomplete. It explains output content well (aided by the output schema) but does not help an agent understand how to supply most inputs. The inclusion of the plan format hint is helpful but insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage across 14 parameters, the description only clarifies granularity (8/16/32) and the centre enum (area/grid). Critical parameters like school, northAngle, declination, entranceMethod, and the structure of coords/boundary are left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (compass zones split into 8/16/32 sectors) and what each zone returns, which is specific enough to identify the tool's function. It does not explicitly differentiate from siblings like vastu_mandala or vastu_plan, but the opening sentence makes the core purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage by requiring a plan in the /vastu/plan format and explaining that zones will list rooms and fixtures, giving some context. However, it does not say when to use this tool versus related tools like vastu_mandala or vastu_rooms, nor does it provide exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools