Skip to main content
Glama

Panchang: Pancha Pakshi (five birds)

astroway_vedic_panchang_pancha_pakshi
Read-onlyIdempotent

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
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
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
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context. It does supply two things annotations cannot: the 20-credit / Tier 2 cost and the concrete shape of the computation (sunrise-anchored day, five yamas, five sub-periods per yama). What it omits — timezone handling, failure modes, response size — is largely covered in the schema or output schema.

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?

A single long but well-formed sentence front-loads the core output description, followed by a compact bracketed block carrying group, endpoint, required fields and cost. The main sentence is dense with nested clauses and could be split for readability, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with an output schema and full annotation coverage, this description leaves nothing critical unexplained: it states the required inputs, the two operating modes, what the response contains, and the credit cost. The agent has enough to decide to call it and to know which of the three personalization routes to take.

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?

Schema description coverage is 69% and the property descriptions are already detailed (for example `bird` records that it wins over `birth` and `janmaNakshatra`). The description still adds meaning by presenting the three mutually exclusive personalization routes as a set and by pairing `janmaNakshatra` with `birthPaksha`, which tells the agent these must be sent together. The required trio (date, latitude, longitude) is restated in the bracketed block.

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 a specific system (Tamil five-bird Pancha Pakshi) and enumerates exactly what is computed: the paksha at sunrise, five day and five night yamas, and each bird's activity per yama, plus the personalized variant. It is clearly distinguishable from other panchang siblings such as tithi, yoga or gowri, though it never explicitly names or contrasts them.

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?

Usage is implied rather than stated: date + place for the general case, and a person (via `bird`, `birth`, or `janmaNakshatra` + `birthPaksha`) for the personalized case. There is no explicit when-to-use, when-not-to-use, or routing advice versus the other vedic_panchang tools, so the agent must infer the choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources