Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Panchang: Pancha Pakshi (five birds)

astroway_vedic_panchang_pancha_pakshi
Read-onlyIdempotent

Calculate Tamil five-bird Pancha Pakshi activities for a date and place, including sunrise paksha, day and night yamas, and optional birth-bird sub-periods.

Instructions

Tamil five-bird system for a date and place: the paksha at sunrise, five day and five night yamas, the activity (ruling, eating, walking, sleeping, dying) of every bird in each, and, with a person (bird, birth, or janmaNakshatra + birthPaksha), that bird's activity and the five sub-periods of each yama.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/pancha-pakshi] [Required: date, 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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_panchang_pancha_pakshi"
  }
}

Input Schema

NameRequiredDescriptionDefault
birdNoThe birth bird directly; wins over birth and janmaNakshatra. Use it where your tradition groups the stars differently.
dateYesCivil date, YYYY-MM-DD. The day runs from its sunrise to the next sunrise.
birthNo
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.
longitudeYes
ayanamsaIdNo
birthPakshaNoPaksha at birth, with janmaNakshatra.
janmaNakshatraNoBirth star 1 to 27, with birthPaksha, when birth is not sent.
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
birdNo
dateNo
basisNo
yamasNo
methodNo
pakshaNo
sourceNo
sunsetNo
sunriseNo
weekdayNo
activitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent, non-open-world read. The description adds useful behavioral context beyond them: it explains the returned Panchang structure and how the output expands when a person is specified, and it discloses the 20-credit cost.

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 definition is front-loaded and efficient, with a dense but purposeful opening sentence followed by compact metadata lines for group, endpoint, required fields, and cost. The main sentence is long, but every clause contributes useful scope or output information.

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 an 11-parameter tool with an output schema, the description covers the core purpose, required inputs, optional person modes, output structure, and cost. It is largely complete, though it could better explain when this tool should be chosen over related Panchang tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning by grouping the three ways to specify a person (`bird`, `birth`, or `janmaNakshatra` + `birthPaksha`) and explaining that this changes the output. With 11 parameters and only 64% schema description coverage, it still leaves several parameters such as `ayanamsa`, `timezone`, and `timezoneOffset` to the schema.

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 states a specific resource and scope: the Tamil five-bird Pancha Pakshi system for a date and place, including the paksha, day/night yamas, and each bird's activities. It is clearly distinguishable from other Panchang siblings by its five-bird focus, though it lacks an explicit verb and does not name alternative tools.

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?

It implicitly indicates when to supply person-related parameters by saying that providing `bird`, `birth`, or `janmaNakshatra` plus `birthPaksha` adds that bird's activity and yama sub-periods. However, it gives no explicit when-to-use versus alternatives guidance or exclusions.

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