AstroTune — Vedic astrology (Jyotish)

life_events

ЧЕЛОВЕК НАЗВАЛ ДАТЫ СВОИХ СОБЫТИЙ («переехал в феврале 2018», «женился в 2021»): какие махадаша и антардаша шли на каждую, одним вызовом. День не обязателен: 2018-02 или 2018. Нужно время рождения. Весь ряд периодов — dasha_timeline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`lang`	No		ru
`time`	No
`place`	No
`events`	Yes	события человека: дата и подпись
`ayanamsa`	No		Lahiri
`chart_id`	No
`geonameid`	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.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / utc_offset

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

Changed8 schema fields changedSep 24, 2026

removedInput schema / $defs / Sobytie / description

Removed value: -"Одно событие жизни: дата и, если хочется, подпись.\n\n🔴🔴 ЗАЧЕМ ОТДЕЛЬНЫЙ ВИД, А НЕ `list[dict[str, str]]`. Замер 22.09.2026 набором живых\nвопросов (#5743): `life_events` не выбирала НИ ОДНА из трёх семей моделей — на «я\nпереехал в феврале 2018 и женился в июле 2021» они либо не звали ничего, либо брали\n`dasha_timeline`. Свободный словарь в схеме выглядит как «сюда что-нибудь положите»:\nмодель не видит, из каких полей собрать событие, и выбирает соседний инструмент с\nпонятными параметрами. Названный вид печатает в схеме `date` и `label`."

removedInput schema / properties / chart_id / default
```
Removed value: -null
```
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: -"life_eventsDictOutput"
```

Changed5 schema fields changedSep 22, 2026

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 / $defs / Sobytie / properties / date / title
```
Removed value: -"Date"
```
- removedInput schema / $defs / Sobytie / properties / label / title
```
Removed value: -"Label"
```
- removedInput schema / $defs / Sobytie / title
```
Removed value: -"Sobytie"
```
- removedInput schema / properties / ayanamsa / title
```
Removed value: -"Ayanamsa"
```
- 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 / events / title
```
Removed value: -"Events"
```
- 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 / title
```
Removed value: -"life_eventsArguments"
```

Changed5 schema fields changedSep 22, 2026

addedInput schema / $defs

Added value: +{
+  "Sobytie": {
+    "description": "Одно событие жизни: дата и, если хочется, подпись.\n\n🔴🔴 ЗАЧЕМ ОТДЕЛЬНЫЙ ВИД, А НЕ `list[dict[str, str]]`. Замер 22.09.2026 набором живых\nвопросов (#5743): `life_events` не выбирала НИ ОДНА из трёх семей моделей — на «я\nпереехал в феврале 2018 и женился в июле 2021» они либо не звали ничего, либо брали\n`dasha_timeline`. Свободный словарь в схеме выглядит как «сюда что-нибудь положите»:\nмодель не видит, из каких полей собрать событие, и выбирает соседний инструмент с\nпонятными параметрами. Названный вид печатает в схеме `date` и `label`.",
+    "properties": {
+      "date": {
+        "description": "когда это было: ГГГГ-ММ-ДД, ГГГГ-ММ или ГГГГ",
+        "title": "Date",
+        "type": "string"
+      },
+      "label": {
+        "default": "",
+        "description": "чем это было: переезд, свадьба, смена работы",
+        "title": "Label",
+        "type": "string"
+      }
+    },
+    "required": [
+      "date"
+    ],
+    "title": "Sobytie",
+    "type": "object"
+  }
+}

addedInput schema / properties / events / description

Added value: +"события человека: дата и подпись"

addedInput schema / properties / events / items / $ref
```
Added value: +"#/$defs/Sobytie"
```
removedInput schema / properties / events / items / additionalProperties
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / events / items / type
```
Removed value: -"object"
```

First observedSep 22, 2026

TDQS

A3.8/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 behavioral burden. It does disclose a real prerequisite (birth time is required) and the flexibility of the date format, but it says nothing about whether the call is read-only, how many periods are returned per event, or any limits — leaving meaningful behavioral gaps for a no-annotation tool.

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?

Dense and front-loaded: purpose, then date-format guidance, then prerequisite, then the sibling alternative — no filler. Slightly terse in places (the prerequisite could be more prominent) but every sentence earns its place.

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?

For a 9-parameter tool with an output schema, the description covers the core contract (events in, dasha periods out) and the birth-time requirement. It is incomplete on the multiplicity of ways to supply time/place (chart_id, geonameid, place, utc_offset) and on the recovery path hinted at by the utc_offset schema note (time_ambiguous), which the agent needs in the failure case.

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 22%, so the description must compensate, and it does add value by explaining the event date granularity (2018-02 or 2018, day optional) and the birth-time requirement. However, it says nothing about lang, ayanamsa, chart_id vs geonameid/place/utc_offset, or how those alternative location/time inputs interact, leaving most of the 9 parameters unexplained.

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?

States a specific verb and resource: given a person's life-event dates, it returns the mahadasha/antardasha running for each in one call. It explicitly names the sibling it is not (dasha_timeline) and gives concrete examples («переехал в феврале 2018»), so an agent can distinguish it from the 19 sibling tools without opening the schema.

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?

Routes the agent explicitly: use this tool when the person has supplied event dates, and use dasha_timeline for the full series of periods. The condition is clear but there are no exclusions or additional preconditions beyond 'requires birth time'.

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?