Skip to main content
Glama

explore_vedic_chart

Read-onlyIdempotent

Generate an interactive Vedic birth chart as a clickable South Indian Rashi grid, revealing sidereal placements, nakshatras, and Lagna with precise ephemeris data.

Instructions

Generate an interactive Vedic (Jyotish) birth chart as a South Indian fixed-sign Rashi grid, with clickable rashis showing sidereal placements, nakshatras, and the Lagna.

CREDIT COST: 3 credits per call (chart calculation + visual render).

Returns an embedded visual explorer that lets you click any rashi cell for its themes and any planets placed there. Shows sidereal (Lahiri by default) planet placements, nakshatra with pada, navamsa, and the Lagna (Ascendant) rashi. Uses NASA JPL DE440 ephemerides. Use this for a rich, interactive Jyotish experience in MCP Apps-capable hosts (Claude Desktop). Falls back to a text summary in other hosts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ayanamsaNoAyanamsa system for sidereal conversion. Defaults to 'lahiri'.
datetimeYesISO 8601 birth datetime in UTC, e.g. '1990-06-15T14:30:00Z'. Include 'Z' or a timezone offset.
latitudeNoBirth 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.
locationNoBirth 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.
timezoneNoIANA timezone name for the birth location (e.g. 'Asia/Kolkata'). Recommended for accuracy if providing local birth time without a UTC offset.
longitudeNoBirth longitude in decimal degrees (positive = East). Optional if `location` is a place name.
Behavior5/5

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

Annotations already declare safe read-only and idempotent hints, lowering the bar. The description adds credit cost, interactive click behavior, fallback to text in unsupported hosts, and use of NASA JPL DE440 ephemerides — rich behavioral detail beyond annotations. No contradictions.

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 well-structured and front-loaded: main purpose, credit cost, features, technical basis, usage context, and fallback in clear separate pieces. Every sentence earns its place with no redundancy.

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 complex tool with no output schema, the description covers the key return type (interactive visual explorer), fallback behavior, and precision details. It lacks explicit error handling or exact return structure, but given the rich schema and annotations, it is sufficiently complete.

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?

All six parameters have comprehensive descriptions in the schema (100% coverage), so the baseline is 3. The description does not add parameter-specific semantics beyond mentioning 'Lahiri by default', which duplicates the schema.

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 clearly states it generates an interactive Vedic (Jyotish) birth chart as a South Indian fixed-sign Rashi grid, with clickable rashis. This specific verb+resource+format distinguishes it from siblings like vedic_chart and explore_natal_chart.

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?

Provides clear context: use for a rich, interactive Jyotish experience in MCP Apps-capable hosts, with fallback to text in other hosts. However, it does not explicitly compare to alternatives like vedic_chart or ephemeris_natal_chart, so it stops short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openephemeris/openephemeris-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server