Skip to main content
Glama
Dinesh-Gahlot

mcp-indian-astrology

divine_get_planet_combustion_transit

Read-onlyIdempotent

Identify when a planet is combust (Asta) during transit and get the combustion periods with their effects, using birth details to determine strength loss.

Instructions

Get planet combustion (Asta) transit details for a specific planet.

Combustion occurs when a planet is too close to the Sun and loses strength. Returns combustion periods and their effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesBirth day (e.g., '24')
lanNoLanguage codeen
latYesLatitude (e.g., '28.7041')
lonYesLongitude (e.g., '77.1025')
minYesBirth minute (e.g., '40')
secNoBirth second0
hourYesBirth hour in 24h format (e.g., '14')
yearYesBirth year (e.g., '1990')
monthYesBirth month (e.g., '05')
placeYesBirth place (e.g., 'New Delhi')
tzoneYesTimezone offset (e.g., '5.5')
genderYesGender: 'male' or 'female'
planetYesPlanet: mars, mercury, jupiter, venus, or saturn
full_nameYesFull name of the person

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, non-destructive operation. The description adds useful domain context (combustion occurs when a planet is too close to the Sun) and states that it returns 'combustion periods and their effects,' which mildly supplements the annotation coverage. No additional behavioral traits like rate limits or auth constraints are mentioned.

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 succinct—two short sentences—and the main action is front-loaded in the first sentence. The second sentence provides a clear, concise explanation of combustion without bloat. No unnecessary words or repetition.

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?

Given the presence of an output schema and full schema coverage, the description covers the essential concept and purpose. However, it does not clarify what 'effects' means or expand on the 'Asta' term, and it offers no usage hints for the many parameters. The combination of schema and annotations makes it mostly complete, but the description alone would leave some gaps for an agent.

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 schema comprehensively documents all 14 parameters, including planet and birth details. The description adds no parameter-specific guidance beyond the schema, so it rests at the baseline score of 3.

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 states a specific verb and resource: 'Get planet combustion (Asta) transit details for a specific planet.' It explains the meaning of combustion, which clearly differentiates this from other transit tools like retrograde or nakshatra transit. However, it does not explicitly name any sibling tool, so the differentiation is implied rather than explicit.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives such as divine_get_planet_retrograde_transit or divine_get_grah_gochar. The only implied usage is 'when combustion details are needed,' but there are no when-not conditions or references to sibling tools, leaving the agent to infer the appropriate context.

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