Vedaksha

Overview Schema Source Related Servers Discussions Admin

compute_combustion

Read-only

Determine each planet's combustion state in Vedic astrology—Combust, DeeplyCombust, or None—using sidereal longitudes and retrograde flags, with separation degrees for six planets.

Instructions

Compute combustion state for each planet relative to the Sun: principle per BPHS Ch.7 vv.28-29, orbs per Surya Siddhanta IX.6-8 and X.1 (Moon 12, Mars 17, Mercury 14 or 12 retrograde, Jupiter 11, Venus 10 or 8 retrograde, Saturn 15 deg). Returns Combust, DeeplyCombust, or None for Moon, Mars, Mercury, Jupiter, Venus, Saturn with degrees of separation. This is a low-level tool over already-known positions, not a natal-chart tool: call compute_natal_chart first and pass its planets[].longitude (matched by planets[].name) and planets[].retrograde values straight through as this tool's inputs — do not recompute or re-derive them.

Input Schema

TableJSON Schema

Name	Required	Description
`sun`	Yes	Sidereal longitude of Sun [0, 360). From compute_natal_chart's planets[] entry where name == "Sun", field longitude.
`mars`	Yes	Sidereal longitude of Mars [0, 360). From compute_natal_chart's planets[] entry where name == "Mars", field longitude.
`moon`	Yes	Sidereal longitude of Moon [0, 360). From compute_natal_chart's planets[] entry where name == "Moon", field longitude.
`venus`	Yes	Sidereal longitude of Venus [0, 360). From compute_natal_chart's planets[] entry where name == "Venus", field longitude.
`saturn`	Yes	Sidereal longitude of Saturn [0, 360). From compute_natal_chart's planets[] entry where name == "Saturn", field longitude.
`jupiter`	Yes	Sidereal longitude of Jupiter [0, 360). From compute_natal_chart's planets[] entry where name == "Jupiter", field longitude.
`mercury`	Yes	Sidereal longitude of Mercury [0, 360). From compute_natal_chart's planets[] entry where name == "Mercury", field longitude.
`mars_retrograde`	No	True if Mars is retrograde. Accepted for symmetry; Mars's orb is 17 deg either way (Surya Siddhanta IX.6 gives it no retrograde figure), so this does not change the result. From compute_natal_chart's Mars entry, field retrograde.
`venus_retrograde`	No	True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg (Surya Siddhanta IX.7). From compute_natal_chart's Venus entry, field retrograde.
`saturn_retrograde`	No	True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 15 deg either way, so this does not change the result. From compute_natal_chart's Saturn entry, field retrograde.
`jupiter_retrograde`	No	True if Jupiter is retrograde. Accepted for symmetry; Jupiter's orb is 11 deg either way, so this does not change the result. From compute_natal_chart's Jupiter entry, field retrograde.
`mercury_retrograde`	No	True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (Surya Siddhanta IX.8). From compute_natal_chart's Mercury entry, field retrograde.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`states`	Yes	One entry per graha other than the Sun.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv9.1.2Sep 15, 2026

changedInput schema / properties / mars_retrograde / description

Previous value: -"True if Mars is retrograde, which narrows its combustion orb from 17 deg to 8 deg. From compute_natal_chart's Mars entry, field retrograde."New value: +"True if Mars is retrograde. Accepted for symmetry; Mars's orb is 17 deg either way (Surya Siddhanta IX.6 gives it no retrograde figure), so this does not change the result. From compute_natal_chart's Mars entry, field retrograde."

changedInput schema / properties / mercury_retrograde / description

Previous value: -"True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (BPHS Ch. 7 vv. 28-29). From compute_natal_chart's Mercury entry, field retrograde."New value: +"True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (Surya Siddhanta IX.8). From compute_natal_chart's Mercury entry, field retrograde."

changedInput schema / properties / saturn_retrograde / description

Previous value: -"True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 16 deg either way, so this does not change the result. From compute_natal_chart's Saturn entry, field retrograde."New value: +"True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 15 deg either way, so this does not change the result. From compute_natal_chart's Saturn entry, field retrograde."

changedInput schema / properties / venus_retrograde / description

Previous value: -"True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg. From compute_natal_chart's Venus entry, field retrograde."New value: +"True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg (Surya Siddhanta IX.7). From compute_natal_chart's Venus entry, field retrograde."

Changed12 schema fields changedv8.0.1Sep 3, 2026

changedInput schema / properties / jupiter / description

Previous value: -"Sidereal longitude of Jupiter [0, 360)"New value: +"Sidereal longitude of Jupiter [0, 360). From compute_natal_chart's planets[] entry where name == \"Jupiter\", field longitude."

changedInput schema / properties / jupiter_retrograde / description

Previous value: -"True if Jupiter is retrograde. Accepted for symmetry; Jupiter's orb is 11 deg either way, so this does not change the result"New value: +"True if Jupiter is retrograde. Accepted for symmetry; Jupiter's orb is 11 deg either way, so this does not change the result. From compute_natal_chart's Jupiter entry, field retrograde."

changedInput schema / properties / mars / description

Previous value: -"Sidereal longitude of Mars [0, 360)"New value: +"Sidereal longitude of Mars [0, 360). From compute_natal_chart's planets[] entry where name == \"Mars\", field longitude."

changedInput schema / properties / mars_retrograde / description

Previous value: -"True if Mars is retrograde, which narrows its combustion orb from 17 deg to 8 deg"New value: +"True if Mars is retrograde, which narrows its combustion orb from 17 deg to 8 deg. From compute_natal_chart's Mars entry, field retrograde."

changedInput schema / properties / mercury / description

Previous value: -"Sidereal longitude of Mercury [0, 360)"New value: +"Sidereal longitude of Mercury [0, 360). From compute_natal_chart's planets[] entry where name == \"Mercury\", field longitude."

changedInput schema / properties / mercury_retrograde / description

Previous value: -"True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (BPHS Ch. 7 vv. 28-29)"New value: +"True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (BPHS Ch. 7 vv. 28-29). From compute_natal_chart's Mercury entry, field retrograde."

changedInput schema / properties / moon / description

Previous value: -"Sidereal longitude of Moon [0, 360)"New value: +"Sidereal longitude of Moon [0, 360). From compute_natal_chart's planets[] entry where name == \"Moon\", field longitude."

changedInput schema / properties / saturn / description

Previous value: -"Sidereal longitude of Saturn [0, 360)"New value: +"Sidereal longitude of Saturn [0, 360). From compute_natal_chart's planets[] entry where name == \"Saturn\", field longitude."

changedInput schema / properties / saturn_retrograde / description

Previous value: -"True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 16 deg either way, so this does not change the result"New value: +"True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 16 deg either way, so this does not change the result. From compute_natal_chart's Saturn entry, field retrograde."

changedInput schema / properties / sun / description

Previous value: -"Sidereal longitude of Sun [0, 360)"New value: +"Sidereal longitude of Sun [0, 360). From compute_natal_chart's planets[] entry where name == \"Sun\", field longitude."

changedInput schema / properties / venus / description

Previous value: -"Sidereal longitude of Venus [0, 360)"New value: +"Sidereal longitude of Venus [0, 360). From compute_natal_chart's planets[] entry where name == \"Venus\", field longitude."

changedInput schema / properties / venus_retrograde / description

Previous value: -"True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg"New value: +"True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg. From compute_natal_chart's Venus entry, field retrograde."

Changed6 schema fields changedv8.0.0Aug 29, 2026

addedInput schema / properties / jupiter_retrograde / description

Added value: +"True if Jupiter is retrograde. Accepted for symmetry; Jupiter's orb is 11 deg either way, so this does not change the result"

addedInput schema / properties / mars_retrograde / description

Added value: +"True if Mars is retrograde, which narrows its combustion orb from 17 deg to 8 deg"

addedInput schema / properties / mercury_retrograde / description

Added value: +"True if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (BPHS Ch. 7 vv. 28-29)"

addedInput schema / properties / saturn_retrograde / description

Added value: +"True if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 16 deg either way, so this does not change the result"

addedInput schema / properties / venus_retrograde / description

Added value: +"True if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "states": {
+      "description": "One entry per graha other than the Sun.",
+      "items": {
+        "properties": {
+          "degrees_from_sun": {
+            "description": "Angular separation from the Sun in degrees.",
+            "type": "number"
+          },
+          "planet": {
+            "description": "Graha assessed.",
+            "type": "string"
+          },
+          "state": {
+            "description": "Combust, DeeplyCombust, or None.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "state",
+          "degrees_from_sun"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "states"
+  ],
+  "type": "object"
+}

First observedv7.0.0Aug 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already set readOnlyHint=true, and the description adds substantial behavioral context: the tool consumes already-computed positions, uses specific orbs from named sources, returns statuses per planet, and notes which retrograde flags are accepted for symmetry but do not change the result. No contradiction with annotations.

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 dense but every clause earns its place: it states the computation, cites sources, lists orbs, names outputs, and gives critical usage constraints. It is front-loaded with the core purpose and ends with the most important operational caveat about not recomputing inputs.

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?

For a 12-parameter tool with a full output schema and read-only annotation, the description is complete: it specifies the required upstream computation, the input semantics, the orbital rules, the result categories, and the exact way to feed data in. An agent has everything needed to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds valuable mapping guidance on top: all longitude and retrograde inputs should be copied directly from compute_natal_chart's planets[] array matched by name, and it clarifies that some retrograde parameters are accepted but inert. This supplements the schema rather than merely repeating it.

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?

Description uses a specific verb and resource: 'Compute combustion state for each planet relative to the Sun.' It names the exact outputs (Combust, DeeplyCombust, or None) and planets involved, and explicitly distinguishes itself from a natal-chart tool, which separates it from sibling tools like compute_natal_chart.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: this is a low-level tool over already-known positions, not a natal-chart tool. It instructs the agent to call compute_natal_chart first and pass planets[].longitude and retrograde values straight through, and tells it not to recompute or re-derive them.

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

Deploy Server