Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Muhurat: Marriage (Vivah)

astroway_vedic_muhurat_marriage
Read-onlyIdempotent

Scan a date range for auspicious marriage muhurat days, score each by Tithi, Vara, Nakshatra, Yoga, and Karana, and return top-ranked dates with Abhijit sub-windows.

Instructions

Auspicious-window scanner for marriage (Vivah Muhurat) over a date range. Scores each day by Tithi + Vara + Nakshatra + Yoga + Karana per Muhurta Chintamani Adhyaya 5 + B.V.Raman Muhurta Ch.6. Preferred nakshatras: Rohini/Mrigashira/Magha/Hasta/Swati/Anuradha/Mula/U.Phalguni/U.Ashadha/U.Bhadrapada/Revati. Avoid Sun/Tue/Sat. Returns top-N days sorted by score with per-day Abhijit Muhurat sub-window.

[Group: Vedic] [Endpoint: POST /v1/vedic/muhurat/marriage] [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_marriage"
  }
}

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is lifted; the description adds substantive behavior — the exact five-limb scoring basis, the classical sources, and the return shape (top-N sorted by score with a per-day Abhijit sub-window). It omits the 50-credit Tier-3 cost and any accuracy caveat about geo coordinates, which are decision-relevant for an agent.

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?

Front-loaded with purpose, then scoring method, then selection preferences, then output shape. Every clause carries information; no filler or restatement of the title.

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?

An output schema exists, so return-value detail is optional (and it provides some anyway), and annotations cover safety. The gap is input-side: with 8 parameters and one required, the description leaves the geo/timezone defaults and their impact on the computed muhurat unexplained, which an agent needs to call this correctly.

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?

Schema description coverage is only 25%, so the description must compensate and largely doesn't. 'Top-N' and 'date range' loosely map to topN and search_window_start/end, but latitude/longitude default to 0 (equator/UTC) — a setting that would silently distort the Abhijit sub-window and day boundaries — and the description never says coordinates matter or how ayanamsa selection affects scoring.

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?

Names a specific verb+resource ('Auspicious-window scanner for marriage (Vivah Muhurat)') plus the scope ('over a date range'). Against a large sibling family of event-specific muhurat tools (business_start, surgery, travel, vehicle_purchase…), the marriage/Vivah anchor makes selection unambiguous.

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?

Clearly frames the use case (finding marriage dates) and gives inline selection heuristics — the preferred nakshatra list and the 'avoid Sun/Tue/Sat' rule. It never names a sibling as the alternative (e.g. general_auspicious for non-marriage events), so routing depends on the agent inferring the event-type suffix.

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