AstroTune — Vedic astrology (Jyotish)

life_events

ЗОВИТЕ, КОГДА ЧЕЛОВЕК НАЗВАЛ СВОИ ДАТЫ: «переехал в феврале 2018», «женился в июле 2021», «сменил работу в ноябре 2024». По каждой дате отвечает, какая махадаша и антардаша тогда действовали, — одним вызовом на все события сразу. ⭐ ДЕНЬ ЗНАТЬ НЕ ОБЯЗАТЕЛЬНО: «февраль 2018» пишется как 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

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.5/5.0

Behavior5/5

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

No annotations were provided, so the description carries the full burden of behavioral disclosure, and it delivers richly: 'NOTHING IS SAVED: events come in the request and go with the response, not a line remains on the server'; 'NOTHING IS INTERPRETED: the coincidence of a period with an event doesn't prove a connection — a period lasts for years'; plus partial-month handling behavior ('If the period changed within a month, both will come and the transition moment') and the birth-time prerequisite. This exceeds what annotations would typically convey.

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 longer than average, but every sentence earns its place: trigger, core behavior, date flexibility, sibling differentiation, data-handling guarantee, interpretation warning, and prerequisite. It is front-loaded with the trigger condition and uses emoji and all-caps markers to structure the key warnings. It is verbose in places (the repeated ⛔ blocks could be tightened) but never padded with filler.

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

Completeness4/5

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

Given the tool's complexity (8 parameters, 13% schema coverage) and that an output schema exists, the description covers nearly everything an agent needs: when to call, what it returns (dasha pairs per date, with transition moments), what it does NOT do (save, interpret), and the birth-time prerequisite. The only gap is the undocumented ancillary parameters, which are likely shared tool-family conventions rather than life_events-specific knowledge.

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 13%, so the description must compensate, and it does for the core parameter: it precisely explains the events.date format ('February 2018 is written as 2018-02, year as 2018') and the batch nature of events ('one call for all events at once'). However, it leaves the ancillary parameters (lang, time, place, ayanamsa, chart_id, geonameid, date) undocumented in the description; these are likely shared conventions across the astro tool family, but with such low coverage the description still leaves those semantics to inference.

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 states a precise verb+resource+scope: 'CALL WHEN A PERSON NAMES THEIR DATES... it answers which mahadasha and antardasha were active then — one call for all events at once.' It is unambiguous about the resource (life events mapped to dasha periods) and explicitly distinguishes itself from the sibling dasha_timeline by naming it and explaining the difference. An agent cannot confuse this tool's purpose with any of the 17 siblings.

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?

The description gives an explicit trigger condition ('CALL WHEN A PERSON NAMES THEIR DATES') and an explicit exclusion with the named alternative: 'Don't confuse with dasha_timeline: that returns the WHOLE series of periods, and you would have to match it with the person's dates yourself; here the matching is already done.' It also states a hard prerequisite: 'Requires a known birth time: without it, the dasha series doesn't exist.' Usage routing is fully specified.

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?