Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Muhurat: Property purchase / Griha Pravesh

astroway_vedic_muhurat_property_purchase
Read-onlyIdempotent

Find auspicious time windows for property purchase or moving into a new home using Vedic muhurat and preferred nakshatras while avoiding Sun, Tue, Sat.

Instructions

Auspicious-window scanner for purchasing or moving into property (Griha Pravesh). Preferred nakshatras: Anuradha/U.Phalguni/U.Ashadha/U.Bhadrapada/Mrigashira/Rohini/Pushya/Hasta/Sravana/Dhanishta/Shatabhisha/Revati. Avoid Sun/Tue/Sat.

[Group: Vedic] [Endpoint: POST /v1/vedic/muhurat/property-purchase] [Required: search_window_start] [Cost: 50 credits (Tier 3)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search_window_start": "<search_window_start>"
    },
    "name": "astroway_vedic_muhurat_property_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNNo
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeNo
longitudeNo
ayanamsaIdNo
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC.
search_window_endNo
search_window_startYes

Output Schema

NameRequiredDescriptionDefault
activityNo
ayanamsaNo
locationNo
search_windowNo
auspiciousWindowsNo
nextAuspiciousWindowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new operational facts: the POST endpoint, the mandatory search_window_start, and the cost of 50 credits (Tier 3), which matters before an agent spends budget. Return shape is left to the output schema, which exists, so that omission is acceptable.

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?

Front-loaded with the purpose, then the practical nakshatra/day rules, then bracketed metadata (group, endpoint, required, cost). The long nakshatra list is dense but domain-relevant rather than filler; every block carries information.

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?

Annotations and an existing output schema relieve the description of safety and return-value burdens, and it discloses cost and the required param. But for an 8-parameter tool at 25% schema coverage it leaves the search window length and location/timezone handling unexplained, which are exactly the inputs an agent could get wrong.

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?

Eight parameters with only 25% schema description coverage, yet the description explains none of them beyond naming search_window_start as required. Critically it never says search_window_end bounds the scan or how topN (default 10, max 60) affects output, and latitude/longitude defaulting to 0 is left ambiguous for a location-sensitive electional scan.

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?

States a specific verb and resource ('auspicious-window scanner for purchasing or moving into property (Griha Pravesh)') and even lists the nakshatras it favours, so the domain is unambiguous. It does not name or contrast any of the near-identical muhurat siblings (business_start, vehicle_purchase, general_auspicious), leaving differentiation to inference from the name.

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?

No when-to-use or when-not guidance. Given a sibling set containing astroway_vedic_muhurat_general_auspicious, vehicle_purchase and investment, the agent gets no rule for choosing this tool over those; the nakshatra/avoid-day rules describe how the scan works, not when to invoke it.

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