mcp-indian-astrology

divine_get_bhava_kundli

Read-onlyIdempotent

Generate a Bhava Kundli house-based chart showing exact house cusps and planetary positions for any birth details. Returns the chart as an SVG or image for Vedic astrology analysis.

Instructions

Get Bhava Kundli (house-based chart) for a given bhava chart number.

Unlike the rashi chart which shows sign placements, the Bhava chart shows exact house cusps and planetary positions within houses. Returns the chart as SVG and image. chart_id is a number from 1 to 12.

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	Bhava chart number: '1' through '12'
`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')

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

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating it returns the chart as SVG and image, and by clarifying the chart_id range (1 to 12). This goes beyond the annotations without contradicting them.

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 front-loaded, with the core purpose in the first sentence. The comparison to the rashi chart and the return-format note are useful, though the 'bhava chart number' phrase in the first sentence is slightly redundant with the later chart_id explanation.

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?

Given the large 19-parameter schema, full schema coverage, an output schema, and strong annotations, the description provides enough additional context to select and invoke the tool. It explains the chart type distinction and output format, while the schema already documents the required birth details and styling options.

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 baseline is 3. The description adds meaning to chart_id by calling it a 'bhava chart number' and noting it ranges from 1 to 12, but that largely repeats the schema. No other parameters receive additional semantic guidance beyond what the schema already provides.

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 names a specific verb and resource: 'Get Bhava Kundli (house-based chart)'. It also differentiates itself from the rashi chart by explaining that Bhava shows exact house cusps and planetary positions within houses, not just sign placements. This clearly separates it from the many chart-related sibling tools.

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?

The description gives explicit comparative guidance: use this chart when you need house cusps and planetary positions within houses, rather than sign placements. It does not name a specific sibling tool or state a when-not condition, but the contrast with the rashi chart gives a clear selection context.

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

Deploy Server