Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Panchang: Rahu Kaal block

astroway_vedic_panchang_rahu_kaal
Read-onlyIdempotent

Find Rahu Kaal, Yamaganda, and Gulika inauspicious time windows plus Abhijit Muhurat for a given date, time, and location using weekday-based sunrise and sunset calculations.

Instructions

Three inauspicious 1.5h-windows (Rahu Kaal + Yamaganda + Gulika) + Abhijit Muhurat. Position depends on weekday and sunrise/sunset.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/rahu-kaal] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

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": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_panchang_rahu_kaal"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
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. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
gulikaNo
sunsetNo
sunriseNo
rahuKaalNo
yamagandaNo
abhijitMuhuratNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior. The description adds real context beyond that: the windows shift with weekday and are anchored to sunrise/sunset, and the metadata line discloses the credit cost (20, Tier 2). It still says nothing about what the response contains or timezone sensitivity, but the computational dependency and cost are useful disclosures.

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?

Two dense sentences lead with what the tool returns, followed by the dependency that governs the values, and the bracketed metadata is compact. No filler, though the parameter list partially duplicates the schema.

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 values need no explanation, and the core inputs plus the sunrise/sunset dependency are covered. However, with 13 parameters of which 9 are optional and unexplained, the description leaves an agent unsure which configuration fields materially change a panchang timing result.

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 23% across 13 parameters, so the description needed to compensate and largely does not. It lists the four required fields (date, time, latitude, longitude) — already visible in the schema — and the note that positions depend on sunrise/sunset implicitly justifies the location/time inputs, but it never addresses whether the many optional fields (zodiacType, houseSystem, ayanamsaId, cosmogram) affect this output or can be ignored.

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 resource set: three inauspicious 1.5-hour windows (Rahu Kaal, Yamaganda, Gulika) plus Abhijit Muhurat. That is concrete and distinguishable from other panchang siblings by content, though it does not explicitly contrast itself with choghadia, hora, or muhurta tools.

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 or when-not guidance and no named alternative. The word 'inauspicious' hints at the application (avoiding those windows for important actions) but the agent must infer it, and nothing says how this differs from astroway_vedic_panchang_choghadia or the muhurat tools.

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