Skip to main content
Glama

Kundlit Vedic Astrology

by com.kundlit
OverviewDiscussionsAdmin

Pancha Pakshi (five-bird) timing

get_pancha_pakshi
Read-onlyIdempotent

Returns a PERSONAL timing schedule under Tamil Pancha Pakshi Shastra: it resolves the person's birth bird (Vulture, Owl, Crow, Cock or Peacock) from their birth details, then returns that day's ten yaamas -- five by day, five by night -- each with the acting bird and activity and a list of sub-periods carrying a 1-10 strength rating plus that bird's relation (friend / same / enemy) to the person's own bird. Use this when the user wants timings tuned to THEM. get_muhurta_timings and get_panchang give the same day's windows for everyone at that place with no birth details; this system is independent of them and the two can disagree. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa for the birth-bird nakshatra); no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Yaama boundaries follow the location's actual sunrise and sunset, so the schedule is place-specific.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDay to schedule, YYYY-MM-DD, years 1200-2400. Omit for today at the given place. The birth fields identify the person; this field picks the day being planned.
placeNoPlace as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitudeNoLatitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
timezoneNoIANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.
longitudeNoLongitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
birth_dateYesBirth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected).
birth_timeYesBirth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / birth_date / description
      Previous value: -"Birth date in the Gregorian calendar, YYYY-MM-DD. Years 1200-2400 are supported (real calendar dates only)."New value: +"Birth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected)."
    • changedInput schema / properties / birth_time / description
      Previous value: -"Local birth time, HH:MM in 24-hour format (00:00-23:59)."New value: +"Birth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart."
    • changedInput schema / properties / date / description
      Previous value: -"Day to evaluate (YYYY-MM-DD, years 1200-2400 supported). Defaults to today at the given place."New value: +"Day to schedule, YYYY-MM-DD, years 1200-2400. Omit for today at the given place. The birth fields identify the person; this field picks the day being planned."
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude in decimal degrees. Use with longitude and timezone when place is not given."New value: +"Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too."
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude in decimal degrees."New value: +"Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted."
    • changedInput schema / properties / place / description
      Previous value: -"Place as free text, e.g. \"Jaipur, Rajasthan, India\". Preferred: it is geocoded server-side. Any city worldwide works."New value: +"Place as free text, \"City, State, Country\" -- e.g. \"Jaipur, Rajasthan, India\". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone, e.g. \"Asia/Kolkata\". Required when latitude/longitude are used."New value: +"IANA timezone name, e.g. \"Asia/Kolkata\" or \"America/New_York\" (never an offset like \"+05:30\"). Required when latitude/longitude are used; ignored when `place` is given."
  2. Changed3 schema fields changed
    • changedInput schema / properties / birth_date / description
      Previous value: -"Birth date in the Gregorian calendar, YYYY-MM-DD."New value: +"Birth date in the Gregorian calendar, YYYY-MM-DD. Years 1200-2400 are supported (real calendar dates only)."
    • changedInput schema / properties / birth_time / description
      Previous value: -"Local birth time, HH:MM in 24-hour format."New value: +"Local birth time, HH:MM in 24-hour format (00:00-23:59)."
    • changedInput schema / properties / date / description
      Previous value: -"Day to evaluate (YYYY-MM-DD). Defaults to today at the given place."New value: +"Day to evaluate (YYYY-MM-DD, years 1200-2400 supported). Defaults to today at the given place."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description details computational specifics (Swiss Ephemeris, Lahiri ayanamsa), rate limits (30 req/min/IP, shared 60/min/IP), place-specificity due to sunrise/sunset, and confirms no writes or auth. This adds significant behavioral context.

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 description is relatively long but every sentence is informative. It could be slightly more concise, but it is well-structured with clear sections and front-loads key information.

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?

Given 7 parameters, no output schema, and complex functionality, the description is highly complete. It explains the output structure (yaamas, acting birds, sub-periods, strength ratings, relations) and operational details, making it self-contained.

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 covers 100% of parameters, so baseline is 3. The description adds value by explaining the roles (e.g., 'birth fields identify the person; date picks the day') and providing geocoding details for place. It enhances understanding beyond schema alone.

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?

The description uses a specific verb 'Returns' and clearly identifies the resource as a 'PERSONAL timing schedule under Tamil Pancha Pakshi Shastra'. It distinguishes the tool from siblings get_muhurta_timings and get_panchang by explaining this tool is personalized.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Use this when the user wants timings tuned to THEM' and contrasts with sibling tools that give generic windows. Also mentions the two systems can disagree, providing clear guidance on when to use.

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

All Kundlit Vedic Astrology toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources