Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

The eight directions

astroway_vastu_shastra_vastu_directions
Read-onlyIdempotent

Get Vastu Shastra guidance for all eight directions, including guardian deity, ruling planet, element, classical use, and effects of water bodies or home extensions, with cited sources.

Instructions

Guardian deity, planet, element, the classical use, the result of a water body and of enlarging the house on each side for the eight directions, each with its source. Elements have no verse and are marked as modern.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesNo
orderNo
directionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context beyond that: a cost of 10 credits (Tier 1), an explicit HTTP endpoint, and the caveat that element entries lack verses and are flagged as modern — a data-quality caveat an agent could not get from structured fields. It stops short of saying whether results are static or paginated, but with an output schema present that gap is minor.

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 content sentence is dense but well-packed, and the bracketed metadata (group, endpoint, cost) is clearly separated and scannable. Leading with a raw list of nouns rather than a verb makes the opener slightly harder to parse, but no sentence is wasted.

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 zero-parameter, read-only reference endpoint with an output schema, the description covers what is needed: the fields returned, the provenance guarantee ('each with its source'), and the one anomaly worth knowing about (elements marked as modern). Only the when-to-use decision is missing, which is a guidance issue rather than a completeness-of-behavior one.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to explain. The description appropriately spends its words on what the fixed response contains rather than inventing input guidance.

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

Purpose3/5

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

The description enumerates the data the tool surfaces (guardian deity, planet, element, classical use, water-body results, house-enlargement results, with sources), which tells an agent this is a reference lookup on the eight directions. However, there is no explicit verb such as 'retrieve' or 'list', and nothing distinguishes it from siblings like vastu_zones or vastu_mandala that also deal with directional reference data. The purpose is inferable but not stated crisply.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no indication of whether this is meant as a standalone reference table, as input to a chart interpretation, or when an agent should prefer it over vastu_zones, vastu_plan, or the feng shui lucky-directions tool. The only routing signal is the repeated '[Group: Vastu Shastra]' label, which groups but does not guide.

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