Skip to main content
Glama
Sign In
openephemeris

Open Ephemeris

by openephemeris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Interactive Vedic Chart Explorer

explore_vedic_chart
Read-onlyIdempotent

Generate an interactive Vedic birth chart with sidereal planetary placements, nakshatra, navamsa, and Lagna from birth details.

Instructions

Use this when the user asks 'show my Vedic chart', 'my kundli', 'my Indian astrology chart', 'what's my nakshatra', 'my sidereal birth chart' or 'what's my lagna'. Returns an interactive South Indian fixed-sign Rashi grid (inline in Claude and ChatGPT; text summary elsewhere) with sidereal (Lahiri by default) placements, nakshatra with pada, navamsa and the Lagna (Ascendant) rashi; click any rashi cell for its themes and the planets placed there. Birthplace may be a place name (location).

CREDIT COST: 3 credits per call (chart + render; +1 to resolve a place name).

Input Schema

NameRequiredDescriptionDefault
ayanamsaNoDefault lahiri.
datetimeYesISO 8601 with a required zone, or local time with `timezone`.
latitudeNoBirth latitude (optional with `location`).
locationNoBirth place name, e.g. 'Mumbai, India'; geocoded. Coordinates win if given.
timezoneNoIANA zone for a local birth time.
longitudeNoBirth longitude (optional with `location`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv4.29.0
    • changedInput schema / properties / ayanamsa / description
      Previous value: -"Ayanamsa system for sidereal conversion. Defaults to 'lahiri'."New value: +"Default lahiri."
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 birth datetime in UTC, e.g. '1990-06-15T14:30:00Z'. Must include 'Z' or a timezone offset."New value: +"ISO 8601 with a required zone, or local time with `timezone`."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Takes decimal degrees, not a place name."New value: +"Birth latitude (optional with `location`)."
    • changedInput schema / properties / location / description
      Previous value: -"Birth location as a plain place name like 'Mumbai, India'; the server resolves it to coordinates and timezone (ambiguous names are rejected with a disambiguation hint). Supplied coordinates take precedence over it."New value: +"Birth place name, e.g. 'Mumbai, India'; geocoded. Coordinates win if given."
    • changedInput schema / properties / longitude / description
      Previous value: -"Birth longitude in decimal degrees (positive = East). Optional if `location` is a place name."New value: +"Birth longitude (optional with `location`)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone name for the birth location (e.g. 'Asia/Kolkata'). Used to convert a local birth time without a UTC offset."New value: +"IANA zone for a local birth time."
  2. Changed4 schema fields changedv4.24.2
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 birth datetime in UTC, e.g. '1990-06-15T14:30:00Z'. Include 'Z' or a timezone offset."New value: +"ISO 8601 birth datetime in UTC, e.g. '1990-06-15T14:30:00Z'. Must include 'Z' or a timezone offset."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Never recall coordinates from memory; either supply a place name or resolve with location_search first."New value: +"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Takes decimal degrees, not a place name."
    • changedInput schema / properties / location / description
      Previous value: -"Birth location. Prefer a plain place name like 'Mumbai, India' — the server resolves it via the same lookup `location_search` uses (unambiguous names → coords + timezone; ambiguous names throw with a disambiguation hint). Supplied coords always win."New value: +"Birth location as a plain place name like 'Mumbai, India'; the server resolves it to coordinates and timezone (ambiguous names are rejected with a disambiguation hint). Supplied coordinates take precedence over it."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone name for the birth location (e.g. 'Asia/Kolkata'). Recommended for accuracy if providing local birth time without a UTC offset."New value: +"IANA timezone name for the birth location (e.g. 'Asia/Kolkata'). Used to convert a local birth time without a UTC offset."
  3. Addedv4.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe read-only, idempotent, non-destructive operation. The description adds useful behavior beyond annotations: inline rendering in Claude/ChatGPT, text summary elsewhere, default Lahiri ayanamsa, geocoding via `location`, and credit cost with a possible extra credit for place-name resolution.

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?

The description is front-loaded with usage triggers, then immediately states what is returned and notes the credit cost. It is dense but appropriately sized, with no unnecessary explanation or repetition.

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?

With no output schema, the description carries the burden of explaining the return value and does so well by naming the interactive Rashi grid, sidereal placements, nakshatra/pada, navamsa, and Lagna. It is nearly complete for invocation, though it could clarify how this differs from the sibling `vedic_chart`.

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?

Schema description coverage is 100%, so the schema already documents all six parameters, including datetime format, timezone, coordinates, and location. The description adds only a small amount of meaning, notably that birthplace may be supplied as a place name and that Lahiri is the default ayanamsa.

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 output: an interactive South Indian fixed-sign Rashi grid with sidereal placements, nakshatra/pada, navamsa, and Lagna. It does not explicitly distinguish this interactive explorer from the sibling `vedic_chart`, so it misses full sibling differentiation.

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?

It gives clear trigger phrases such as 'show my Vedic chart', 'my kundli', 'what's my nakshatra', and 'what's my lagna', which directly tell the agent when to use this tool. It does not name when to prefer `vedic_chart` or other chart tools instead.

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