Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Vastu Purusha Mandala (81 padas)

astroway_vastu_shastra_vastu_mandala
Read-onlyIdempotent

Retrieve the 9x9 Vastu Mandala grid with its 45 deities, pada counts and cell assignments for either the Brihat Samhita or Mayamata school, so you can compare how each text allots the outer padas.

Instructions

The 9x9 mandala with all 45 deities, their pada counts and the cells each one holds, for Brihat Samhita or Mayamata. The two texts name four outer padas differently and share the cells out differently (3/2/1 against 6/2/1).

[Group: Vastu Shastra] [Endpoint: POST /v1/vastu/mandala] [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_mandala"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolNo

Output Schema

NameRequiredDescriptionDefault
gridNo
cellsNo
notesNo
schoolNo
sourceNo
devatasNo
brahmasthanNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the substantive behavioral fact that the two schools disagree on names and cell allocation, but says nothing about defaults, response shape, or whether outputs are stable across schools — modest added value over 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?

Two sentences, content front-loaded, and the school-divergence detail is precisely the part an agent could not infer. No filler beyond the boilerplate Group/Endpoint/Cost metadata lines.

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?

An output schema exists, so return values need no explanation, and the single parameter is substantively described. The only missing piece an agent needs to call it correctly is the default/optional behavior of 'school'.

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 description coverage is 0%, so the description must carry the enum semantics, and it does: it maps 'brihat-samhita' and 'mayamata' to their divergence in outer-pada naming and in cell allocation (3/2/1 vs 6/2/1). The one gap is that 'school' is optional yet the description never states the default when it is omitted.

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 names the specific artifact (the 9x9 Vastu Purusha Mandala) and its payload — all 45 deities, their pada counts, and the cells each holds — which clearly separates it from siblings like vastu_directions, vastu_entrance and vastu_rooms. It lacks an explicit verb (e.g. 'returns'), but the resource and content are unambiguous.

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?

Usage is implied: an agent can infer this is the reference lookup for the mandala grid itself, versus the direction/entrance/room tools. However, it gives no explicit when-to-use statement and, more importantly, no guidance on how to choose between the two schools — a decision the description itself raises as consequential.

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