Skip to main content
Glama

Vedic Natal Chart

vedic_chart
Read-onlyIdempotent

Use this when the Vedic / Jyotish chart is wanted as data — 'my sidereal placements as JSON', 'what's my current dasha', 'am I manglik', 'when is my sade sati', 'today's panchang', 'choghadiya today'. Takes coordinates.

Instructions

Use this when the Vedic / Jyotish chart is wanted as data — 'my sidereal placements as JSON', 'what's my current dasha', 'am I manglik', 'when is my sade sati', 'today's panchang', 'choghadiya today'. Takes coordinates. Returns sidereal rashis, nakshatra and pada, navamsa, Whole Sign bhavas; optional dasha, vargas, Manglik, Sade Sati, or the day's panchang with choghadiya and hora.

CREDIT COST: 1 credit per call.

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": {
      "datetime": "<datetime>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "vedic_chart"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.33.0
    • changedInput schema / properties / dasha_as_of / description
      Previous value: -"ISO 8601 instant (UTC if zone-less): add the dasha periods running then."New value: +"ISO 8601 (UTC if zone-less): add the periods running then, maha to prana."
    • changedInput schema / properties / dasha_depth / description
      Previous value: -"1-3: add the Vimshottari dasha tree (1 maha, 2 antar, 3 pratyantar)."New value: +"1-3: add the Vimshottari tree (maha, antar, pratyantar)."
    • addedInput schema / properties / include
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "manglik",
      +      "sade_sati",
      +      "choghadiya",
      +      "hora"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / panchang / description
      Previous value: -"Return the day's panchang instead (tithi, yoga, nakshatra, Rahu Kaal)."New value: +"Return the day's panchang instead (tithi, nakshatra, Rahu Kaal)."
  2. 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."
  3. 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"
      +}
  4. 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)."
  5. 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"
      +}
  6. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds value on top: a stated credit cost of 1 per call, the input contract ('takes coordinates'), and a full inventory of what comes back (sidereal rashis, nakshatra and pada, navamsa, Whole Sign bhavas). With no output schema, this return-shape disclosure is exactly the burden the description should carry.

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?

Front-loaded with the trigger phrase, then a packaged example list, then the return inventory, then cost — a clean and scannable order. The example list is long but each item is a distinct routing signal, and the only mild padding is the redundant restatement of panchang/choghadiya in the return clause.

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 10-parameter tool with no output schema, the description supplies the input contract, the default-family result set, the optional add-ons and the cost — enough to call it correctly. Remaining gaps are minor: no note on birth-time precision requirements or what happens when timezone is omitted alongside a local datetime.

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 90%, so the baseline would be 3, but the description maps optional parameters to outcomes an agent cares about — 'optional dasha, vargas, Manglik, Sade Sati, or the day's panchang with choghadiya and hora' — clarifying the intent of the loosely documented `include` and `panchang` switches. It adds meaning beyond the enum list without restating syntax.

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 opening states the resource and mode precisely — 'the Vedic / Jyotish chart ... as data — JSON' — and the example utterances ('am I manglik', 'today's panchang') concretely anchor what kinds of questions land here. It does not name the sibling explore_vedic_chart, so the data-vs-interpretation split is only implied, which keeps it off a 5.

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?

Explicit selection guidance forward: 'Use this when the Vedic / Jyotish chart is wanted as data', followed by six realistic query triggers covering natal, dasha, manglik, sade sati and panchang/choghadiya cases. There is no stated when-not or named alternative, so routing away from explore_vedic_chart or ephemeris_natal_chart must be inferred.

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