AstroTune — Vedic astrology (Jyotish)

panchanga

Панчанга суток: пять частей — титхи, накшатра, йога, карана и вара — с моментом смены каждой, плюс восход, закат и тяжёлые отрезки (раху-каал, гулика-каал, ямаганда); чогхадии по запросу (detailed). Место — ЛЮБОЕ: название города в city или geonameid из find_place. Без даты берутся сегодняшние сутки этого места.

Input Schema

TableJSON Schema

Name	Required	Default
`city`	No
`date`	No
`lang`	No	ru
`detailed`	No
`podrobno`	No
`geonameid`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / city / 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"
+]

Changed13 schema fields changedSep 22, 2026
- removedInput schema / properties / city / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / city / title
```
Removed value: -"City"
```
- addedInput schema / properties / city / 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 / detailed / title
```
Removed value: -"Detailed"
```
- 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 / podrobno / title
```
Removed value: -"Podrobno"
```
- removedInput schema / title
```
Removed value: -"panchangaArguments"
```
First observedSep 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the default date behavior, location requirements, and the detailed/choghadiya toggle, which is helpful. Yet it does not mention error cases, timezone handling, or what happens when conflicting location parameters are supplied, so transparency is partial.

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 and well-structured: it opens with the core calculation, then lists additional outputs and parameter guidance. Every sentence adds value, with no filler or redundancy.

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 reduces the need to describe return values, and the description covers main usage. Still, key invocation details are missing (date format, lang, podrobno), and with no annotations the description must do more to be fully complete. It is adequate but has clear 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 coverage is 0%, so the description is essential. It explains city, geonameid (from find_place), date default, and detailed (choghadiya). However, it does not explain the meaning/format of the date string, the 'lang' parameter, or the 'podrobno' parameter, leaving important semantic gaps.

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 clearly names the tool's purpose: calculating Panchanga (tithi, nakshatra, yoga, karana, vara) with change moments, plus sunrise, sunset, and Rahu/Gulika/Yamaganda periods. It distinguishes itself from siblings like muhurta_search by describing a specific, concrete resource and output.

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

Usage Guidelines3/5

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

The description gives practical guidance on location (city or geonameid from find_place) and defaults (no date → today). However, it does not explicitly compare this tool to alternatives like muhurta_search, so the 'when vs alternatives' aspect is only implied rather than stated.

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?