AstroTune — Vedic astrology (Jyotish)

chart_transits

Транзиты: где грахи и смена знака (по умолчанию Сатурн, Юпитер, Раху, Кету; Луна — years ≤0.15), ретроградность; nakshatra/combustion — накшатры и сожжение.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`lang`	No		ru
`time`	No
`place`	No
`years`	No
`bodies`	No
`chart_id`	No	Из natal_chart: date, time, place и аянамша — из карты; без него — поля и Lahiri. Поле против карты — отказ input_conflict.
`geonameid`	No
`nakshatra`	No
`combustion`	No
`utc_offset`	No	После отказа time_ambiguous: utc_offset из error.choices.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / combustion

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / nakshatra

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / utc_offset

Added value: +{
+  "description": "После отказа time_ambiguous: utc_offset из error.choices.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / chart_id / description

Previous value: -"chart_id из natal_chart ВМЕСТО date, time и place: берутся из карты вместе с аянамшей. Без него — по полям, аянамша Lahiri. Поля, противоречащие карте, — отказ input_conflict."New value: +"Из natal_chart: date, time, place и аянамша — из карты; без него — поля и Lahiri. Поле против карты — отказ input_conflict."

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / chart_id / description

Previous value: -"chart_id из natal_chart ВМЕСТО date, time и place: берутся из карты вместе с аянамшей. Без него — по полям, аянамша Lahiri."New value: +"chart_id из natal_chart ВМЕСТО date, time и place: берутся из карты вместе с аянамшей. Без него — по полям, аянамша Lahiri. Поля, противоречащие карте, — отказ input_conflict."

Changed9 schema fields changedSep 24, 2026

removedInput schema / properties / bodies / default
```
Removed value: -null
```
removedInput schema / properties / chart_id / default
```
Removed value: -null
```

changedInput schema / properties / chart_id / description

Previous value: -"chart_id из ответа natal_chart. Передайте его ВМЕСТО date, time и place: из карты берутся дата, время, место и аянамша (Raman, KP и т. д.). Без chart_id расчёт идёт по названным полям и в аянамше Lahiri."New value: +"chart_id из natal_chart ВМЕСТО date, time и place: берутся из карты вместе с аянамшей. Без него — по полям, аянамша Lahiri."

removedInput schema / properties / date / default
```
Removed value: -null
```
removedInput schema / properties / geonameid / default
```
Removed value: -null
```
removedInput schema / properties / place / default
```
Removed value: -null
```
removedInput schema / properties / time / default
```
Removed value: -null
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

removedOutput schema / title

Removed value: -"chart_transitsDictOutput"

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / chart_id / description

Added value: +"chart_id из ответа natal_chart. Передайте его ВМЕСТО date, time и place: из карты берутся дата, время, место и аянамша (Raman, KP и т. д.). Без chart_id расчёт идёт по названным полям и в аянамше Lahiri."

Changed6 schema fields changedSep 22, 2026

changedInput schema / properties / bodies / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

changedInput schema / properties / chart_id / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / date / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / geonameid / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

changedInput schema / properties / place / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / time / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed22 schema fields changedSep 22, 2026

removedInput schema / properties / bodies / anyOf

Removed value: -[
-  {
-    "items": {
-      "enum": [
-        "sun",
-        "moon",
-        "mercury",
-        "venus",
-        "mars",
-        "jupiter",
-        "saturn",
-        "rahu",
-        "ketu"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / bodies / items

Added value: +{
+  "enum": [
+    "sun",
+    "moon",
+    "mercury",
+    "venus",
+    "mars",
+    "jupiter",
+    "saturn",
+    "rahu",
+    "ketu"
+  ],
+  "type": "string"
+}

removedInput schema / properties / bodies / title
```
Removed value: -"Bodies"
```
addedInput schema / properties / bodies / type
```
Added value: +"array"
```

removedInput schema / properties / chart_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / chart_id / title
```
Removed value: -"Chart Id"
```
addedInput schema / properties / chart_id / type
```
Added value: +"string"
```

removedInput schema / properties / date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / date / title
```
Removed value: -"Date"
```
addedInput schema / properties / date / type
```
Added value: +"string"
```

removedInput schema / properties / geonameid / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / geonameid / title
```
Removed value: -"Geonameid"
```
addedInput schema / properties / geonameid / type
```
Added value: +"integer"
```
removedInput schema / properties / lang / title
```
Removed value: -"Lang"
```

removedInput schema / properties / place / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / place / title
```
Removed value: -"Place"
```
addedInput schema / properties / place / type
```
Added value: +"string"
```

removedInput schema / properties / time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / time / title
```
Removed value: -"Time"
```
addedInput schema / properties / time / type
```
Added value: +"string"
```
removedInput schema / properties / years / title
```
Removed value: -"Years"
```

removedInput schema / title

Removed value: -"chart_transitsArguments"

First observedSep 22, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose genuine behavioral traits — the default body set, the years ≤ 0.15 gate for the Moon, and that retrogradation is always reported with nakshatra/combustion being opt-in — but it says nothing about cost, latency, output shape (mitigated by the output schema), or whether date/time/place are mandatory in practice.

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?

A single dense sentence that front-loads the core purpose ('Транзиты') and then packs the qualifiers compactly. Nothing is padded, though the parenthetical-heavy structure costs some readability.

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?

The presence of an output schema removes the need to explain return values, and the two schema descriptions (chart_id, utc_offset) cover the trickiest inputs. Still, for an 11-parameter tool with 18% coverage, the description omits any explanation of the date/time/place trio and lang, leaving notable gaps.

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 only 18% across 11 parameters, so the description must compensate. It adds real meaning for a few of them (defaulted bodies, the years threshold governing the Moon), but leaves date, time, place, lang, geonameid, and nakshatra/combustion unflagged in prose, so most parameters remain undocumented.

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 names the resource (transits) and enumerates the concrete outputs it computes: graha positions and sign changes, retrogradation, and optionally nakshatras/combustion. It is far more than a restatement of the name, but it never distinguishes itself from potentially overlapping siblings such as sky_now or panchanga, leaving the agent to infer the boundary.

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?

There is no statement of when to pick this tool over sky_now, dasha_timeline, or panchanga. The only usage-like information is an embedded default (Saturn/Jupiter/Rahu/Ketu) and a threshold (Moon only when years ≤ 0.15), which hints at configuration rather than routing guidance.

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

All AstroTune — Vedic astrology (Jyotish) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?