Skip to main content
Glama
Dinesh-Gahlot

mcp-indian-astrology

divine_get_kundli_transit_moon

Read-onlyIdempotent

Calculate Vedic planetary transits from your birth Moon sign for a specific date. Use the Moon-based reference to understand how current planetary movements influence your life.

Instructions

Get transit analysis from the Moon sign on a chosen transit date.

Shows planetary transits on the given date analyzed from the birth Moon sign, the most commonly used transit reference in Vedic astrology. Optionally set transit time (hour/min/sec) and chart styling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesBirth details
chart_typeNoChart style: 'north' (diamond) or 'south' (square)
line_colorNoChart line color as hex (e.g., '#333333')
sign_colorNoSign label color as hex (e.g., '#333333')
chart_colorNoChart background color as hex (e.g., '#ffffff')
transit_dayYesTransit day (e.g., '24')
transit_minNoTransit minute (e.g., '00')
transit_secNoTransit second (e.g., '00')
planet_colorNoPlanet label color as hex (e.g., '#333333')
transit_hourNoTransit hour in 24h format (e.g., '13')
transit_yearYesTransit year (e.g., '2025')
transit_monthYesTransit month (e.g., '05')
show_planet_retroNoSet '1' to mark retrograde planets on the chart, '0' to hide
show_planet_degreeNoSet '1' to show planet degrees on the chart, '0' to hide

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description's 'Shows planetary transits' aligns with read-only behavior and adds that transit time and chart styling are optional, but it does not disclose additional behavioral nuances such as error conditions or response format.

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?

Three short sentences front-load the core purpose and then add only relevant context: the Moon-sign reference, the most-common-usage note, and optional time/chart settings. There is no filler or repetition of schema details.

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

Completeness5/5

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

Given the rich input schema with all parameters documented, explicit annotations, and an output schema, the description covers the essential use case and optional settings. An agent can call the tool correctly by combining the schema with this description; no critical behavioral information is missing.

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%, with each of the 14 parameters individually described. The description's mention of optional transit time and chart styling adds a useful conceptual grouping but does not add meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the specific operation ('Get transit analysis') and the resource/reference frame ('from the birth Moon sign') on a chosen transit date, which clearly distinguishes it from ascendant-based transit tools like divine_get_kundli_transit_ascendant. The phrase 'the most commonly used transit reference in Vedic astrology' further pins down the tool's scope.

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?

It provides clear context: this tool is for Moon-sign transit analysis on a chosen date, and notes that this reference is the most commonly used in Vedic astrology. It does not explicitly name sibling alternatives or provide exclusion criteria, but the context is sufficient to infer when this tool applies.

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

Deploy Server

Other Tools