mcp-indian-astrology

divine_get_horoscope_chart

Read-onlyIdempotent

Generate a Vedic Kundli chart as SVG or image from birth details. Supports divisional charts D1-D10, chalit, sun, moon, with customizable colors and layout.

Instructions

Generate a Vedic horoscope chart (Kundli diagram) as SVG and image.

Supports divisional charts: D1 (Lagna/Rashi), D2 (Hora), D3 (Drekkana), D9 (Navamsha), D10 (Dashamsha), chalit, sun, moon, and more. Optional styling: chart_type (north/south), hex colors, show_* toggles.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	Birth day (e.g., '24')
`lan`	No	Language code	en
`lat`	Yes	Latitude (e.g., '28.7041')
`lon`	Yes	Longitude (e.g., '77.1025')
`min`	Yes	Birth minute (e.g., '40')
`sec`	No	Birth second	0
`hour`	Yes	Birth hour in 24h format (e.g., '14')
`year`	Yes	Birth year (e.g., '1990')
`month`	Yes	Birth month (e.g., '05')
`place`	Yes	Birth place (e.g., 'New Delhi')
`tzone`	Yes	Timezone offset (e.g., '5.5')
`gender`	Yes	Gender: 'male' or 'female'
`chart_id`	Yes	Chart type: D1 (Lagna), D2 (Hora), D3 (Drekkana), D9 (Navamsha), D10 (Dashamsha), chalit, sun, moon, etc.
`full_name`	Yes	Full name of the person
`chart_type`	No	Chart style: 'north' (diamond) or 'south' (square)
`line_color`	No	Chart line color as hex (e.g., '#333333')
`sign_color`	No	Sign label color as hex (e.g., '#333333')
`chart_color`	No	Chart background color as hex (e.g., '#ffffff')
`planet_color`	No	Planet label color as hex (e.g., '#333333')
`show_planet_retro`	No	Set '1' to mark retrograde planets on the chart, '0' to hide
`show_planet_degree`	No	Set '1' to show planet degrees on the chart, '0' to hide
`show_modern_planets`	No	Set '1' to include Uranus/Neptune/Pluto on the chart, '0' to hide

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.9.1Sep 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds that the tool produces an SVG/image chart and supports styling toggles, which is useful but not deeply detailed. There is no discussion of edge-case behavior such as invalid locations or timezone handling, but the annotation coverage keeps this at an acceptable level.

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 compact and well-structured: the core purpose is front-loaded, then supported chart types and styling options follow. The only minor weakness is the vague 'and more' phrase, but overall each sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 22 parameters, a rich schema, and an output schema, the description covers the main intent and the most important optional controls well enough to make a valid call. The notable gap is the lack of differentiation from the many sibling chart tools, which matters given the crowded context.

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 all 22 parameters are individually documented. The description adds a helpful high-level summary of optional styling controls ('chart_type (north/south), hex colors, show_* toggles') but does not materially enhance the meaning of specific parameters beyond what the schema already provides.

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 clearly states the resource ('Vedic horoscope chart / Kundli diagram'), the output format ('SVG and image'), and enumerates supported chart types (D1, D2, D3, D9, D10, chalit, sun, moon). It is specific and actionable, though it does not explicitly distinguish itself from similarly named siblings like divine_get_matching_horoscope_chart or divine_get_lal_kitab_horoscope_chart.

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

Usage Guidelines3/5

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

The description implies when to use the tool: when a Vedic horoscope chart is requested, including divisional charts and styling options. However, it provides no explicit exclusions or alternatives, and in a large sibling set containing multiple chart tools, it does not guide the agent toward or away from those comparisons.

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

Deploy Server