mcp-indian-astrology

divine_get_kundli_transit_ascendant

Read-onlyIdempotent

Analyze planetary transits from your birth Ascendant for a chosen date to reveal their effects on different life areas. Enter birth details and transit date to get the Lagna-based transit chart.

Instructions

Get transit analysis from the Ascendant (Lagna) on a chosen transit date.

Shows planetary transits on the given date analyzed from the birth Ascendant, indicating effects on different life areas. Optionally set transit time (hour/min/sec) and chart styling.

Input Schema

TableJSON Schema

Name	Required	Description
`params`	Yes	Birth details
`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')
`transit_day`	Yes	Transit day (e.g., '24')
`transit_min`	No	Transit minute (e.g., '00')
`transit_sec`	No	Transit second (e.g., '00')
`planet_color`	No	Planet label color as hex (e.g., '#333333')
`transit_hour`	No	Transit hour in 24h format (e.g., '13')
`transit_year`	Yes	Transit year (e.g., '2025')
`transit_month`	Yes	Transit month (e.g., '05')
`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

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.4/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 meaningful behavioral context by clarifying that the analysis is based on the birth Ascendant, that transit time is optional, and that chart styling can be customized. No contradiction with annotations is present.

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 three sentences with no wasted words. It front-loads the core purpose, then explains what the analysis shows, and finally notes optional settings. Each sentence earns its place and the structure is easy to scan.

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 tool's 14 parameters, the description is appropriately complete because the input schema documents every parameter and an output schema exists. The description explains the essential purpose, the Ascendant-based analysis, and optional transit time/styling. It could name a sibling like divine_get_kundli_transit_moon for extra routing clarity, but that is not essential for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value by grouping the optional transit time components and chart styling settings, and by explaining that the birth details are used to determine the Ascendant from which transits are analyzed. This semantic framing goes beyond the individual parameter descriptions.

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 states a specific verb and resource: 'Get transit analysis from the Ascendant (Lagna) on a chosen transit date.' It clearly differentiates from sibling tools like divine_get_kundli_transit_moon by anchoring the analysis to the birth Ascendant rather than the Moon. The second sentence reinforces the scope by describing what the output covers.

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 provides clear context: use this when you want planetary transit effects analyzed from the birth Ascendant on a given date. It does not explicitly name alternatives or exclusions, but the Ascendant-specific framing is enough to route an agent correctly among the many transit-related siblings.

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

Deploy Server