Skip to main content
Glama
openephemeris

Open Ephemeris

by openephemeris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Vedic Natal Chart

vedic_chart
Read-onlyIdempotent

Compute Vedic/Jyotish chart data from datetime and coordinates, returning sidereal placements, nakshatras with padas, navamsa, bhavas, plus optional Vimshottari dasha and panchang.

Instructions

Use this when the Vedic / Jyotish chart is wanted as data — 'my sidereal placements as JSON', 'nakshatra and pada for every planet', 'my navamsa positions', 'what's my current dasha', 'today's panchang'. Takes coordinates, not a place name. Returns sidereal planet placements in rashis, nakshatras with pada, navamsa placements and bhavas (Whole Sign houses), with Ketu; optional Vimshottari dasha and divisional charts (vargas), or the day's panchang.

CREDIT COST: 1 credit per call.

Input Schema

NameRequiredDescriptionDefault
vargasNoDivisional chart numbers to add, e.g. [9, 10].
ayanamsaNoDefault lahiri.
datetimeYesISO 8601; zone required (`Z`/offset, or local time plus `timezone`).
latitudeYesBirth latitude (+N).
panchangNoReturn the day's panchang instead (tithi, yoga, nakshatra, Rahu Kaal).
timezoneNoIANA zone for a local datetime.
longitudeYesBirth longitude (+E).
dasha_as_ofNoISO 8601 instant (UTC if zone-less): add the dasha periods running then.
dasha_depthNo1-3: add the Vimshottari dasha tree (1 maha, 2 antar, 3 pratyantar).

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 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."New value: +"ISO 8601; zone required (`Z`/offset, or local time plus `timezone`)."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (north positive)."New value: +"Birth latitude (+N)."
    • changedInput schema / properties / longitude / description
      Previous value: -"Birth longitude in decimal degrees (east positive)."New value: +"Birth longitude (+E)."
    • changedInput schema / properties / panchang / description
      Previous value: -"Return the panchang for the local date in datetime instead: tithi, karana, yoga, nakshatra, vara, Rahu Kaal."New value: +"Return the day's panchang instead (tithi, yoga, nakshatra, Rahu Kaal)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise."New value: +"IANA zone for a local datetime."
  2. Changed4 schema fields changedv4.27.0
    • addedInput schema / properties / dasha_as_of
      Added value: +{
+  "description": "ISO 8601 instant (UTC if zone-less): add the dasha periods running then.",
+  "type": "string"
+}
    • addedInput schema / properties / dasha_depth
      Added value: +{
+  "description": "1-3: add the Vimshottari dasha tree (1 maha, 2 antar, 3 pratyantar).",
+  "type": "integer"
+}
    • addedInput schema / properties / panchang
      Added value: +{
+  "description": "Return the panchang for the local date in datetime instead: tithi, karana, yoga, nakshatra, vara, Rahu Kaal.",
+  "type": "boolean"
+}
    • addedInput schema / properties / vargas
      Added value: +{
+  "description": "Divisional chart numbers to add, e.g. [9, 10].",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
  3. Changed2 schema fields changedv4.24.2
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."New value: +"ISO 8601 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (north positive). Resolve from a place name with location_search; never recall coordinates from memory."New value: +"Birth latitude in decimal degrees (north positive)."
  4. Changed3 schema fields changedv4.8.0
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 birth datetime in UTC, e.g. '1990-01-15T08:30:00Z'. Include 'Z' or timezone offset."New value: +"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (north positive)."New value: +"Birth latitude in decimal degrees (north positive). Resolve from a place name with location_search; never recall coordinates from memory."
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise.",
+  "type": "string"
+}
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive status, so the bar is lower, yet the description still adds the 1-credit-per-call cost and the coordinate-not-place-name input requirement. With no output schema, it also carries return-value disclosure and does so by naming the fields produced plus the optional dasha/varga/panchang additions. It does not mention error behavior or ayanamsa defaults, keeping it below a 5.

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 front-loaded with the selection condition, then stacked with output facts, then a one-line cost note that is easy to scan. Each example phrase maps to a distinct capability, so nothing is filler. It is dense but slightly long for the information it carries.

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 a 9-parameter computation tool with no output schema, the description covers what is returned, what is optional, and what input form is required. The remaining gaps (dasha_depth/dasha_as_of interaction, ayanamsa default, panchang mode returning a different shape) are mostly covered by the 100%-covered schema. Panchang being a mode switch rather than an additive option is the one thing worth stating more plainly.

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 coverage is 100%, so baseline would be 3, but the description adds semantics the schema does not: coordinates must be passed rather than resolved from a name, and the optional dasha and varga outputs are conditioned on requesting them. This interprets how the optional parameters change the result rather than restating field names.

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 system (Vedic/Jyotish) and frames it as the 'as data' variant, which implicitly separates it from the sibling explore_vedic_chart. It enumerates concrete outputs (sidereal placements, nakshatra/pada, navamsa, bhavas, Ketu), so the resource is unambiguous. It stops short of naming the contrasting sibling outright.

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?

Quoted trigger phrases ('my sidereal placements as JSON', 'what's my current dasha') give the agent concrete selection cues, and 'Takes coordinates, not a place name' is an actionable precondition that points toward location_search/timezone_resolve. It never explicitly says when NOT to use it (e.g. for the interpretive/exploratory chart), so the sibling routing is left to inference.

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