Ayurveda MCP Server by RoxyAPI

Daily Ayurveda reading - Dosha clock and brahma muhurta by location API

get_ayurveda_daily

Read-only

Get one days Ayurveda reading for a place: sunrise, the brahma muhurta window, the six dosha periods cut from the actual day and night, and the season the date falls in with where each dosha stands in its yearly cycle. It composes the routine and the season routes for one location so a widget needs one call rather than two. The default conventions apply throughout and are echoed; call those two routes directly to choose a different season scheme, zodiac, hemisphere or dosha clock.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Reading date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current day in the timezone parameter.
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`latitude`	Yes	Latitude in decimal degrees. It sets how long the day and the night actually are, which is what the dosha periods are cut from.
`timezone`	No	Selects which day counts as current when date is omitted, and which local day sunrise is computed for. Defaults to UTC, so the reading rolls over at 00:00 UTC. Accepts an IANA name (e.g. "Europe/London"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
`longitude`	Yes	Longitude in decimal degrees. It sets the clock time of sunrise at this place.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`meta`	Yes
`ritu`	Yes
`sunset`	Yes
`sources`	Yes
`summary`	Yes
`sunrise`	Yes
`doshaCycle`	Yes
`conventions`	Yes
`doshaPeriods`	Yes
`brahmaMuhurta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026
- addedInput schema / properties / latitude / maximum
```
Added value: +90
```
- addedInput schema / properties / latitude / minimum
```
Added value: +-90
```
- addedInput schema / properties / longitude / maximum
```
Added value: +180
```
- addedInput schema / properties / longitude / minimum
```
Added value: +-180
```
Changed8 schema fields changedSep 20, 2026
- changedInput schema / examples
```
Previous value: -[
-  {}
-]New value: +[
+  {
+    "latitude": 51.5074,
+    "longitude": -0.1278
+  }
+]
```
- removedInput schema / properties / latitude / maximum
```
Removed value: -90
```
- removedInput schema / properties / latitude / minimum
```
Removed value: --90
```
- changedInput schema / properties / latitude / type
```
Previous value: -[
-  "number",
-  "null"
-]New value: +"number"
```
- removedInput schema / properties / longitude / maximum
```
Removed value: -180
```
- removedInput schema / properties / longitude / minimum
```
Removed value: --180
```
- changedInput schema / properties / longitude / type
```
Previous value: -[
-  "number",
-  "null"
-]New value: +"number"
```
- addedInput schema / required
```
Added value: +[
+  "latitude",
+  "longitude"
+]
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "brahmaMuhurta": {
+      "properties": {
+        "end": {
+          "type": "string"
+        },
+        "start": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "start",
+        "end"
+      ],
+      "type": "object"
+    },
+    "conventions": {
+      "properties": {
+        "doshaClock": {
+          "type": "string"
+        },
+        "hemisphere": {
+          "type": "string"
+        },
+        "rituZodiac": {
+          "type": "string"
+        },
+        "ritucharyaScheme": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "doshaClock",
+        "ritucharyaScheme",
+        "rituZodiac",
+        "hemisphere"
+      ],
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "doshaCycle": {
+      "items": {
+        "properties": {
+          "dosha": {
+            "type": "string"
+          },
+          "state": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "dosha",
+          "state"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "doshaPeriods": {
+      "items": {
+        "properties": {
+          "dosha": {
+            "type": "string"
+          },
+          "end": {
+            "type": "string"
+          },
+          "span": {
+            "type": "string"
+          },
+          "start": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "dosha",
+          "start",
+          "end",
+          "span"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "properties": {
+        "disclaimer": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "disclaimer"
+      ],
+      "type": "object"
+    },
+    "ritu": {
+      "properties": {
+        "ayana": {
+          "type": "string"
+        },
+        "end": {
+          "type": "string"
+        },
+        "gloss": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "phase": {
+          "type": "string"
+        },
+        "sanskritName": {
+          "type": "string"
+        },
+        "start": {
+          "type": "string"
+        },
+        "strength": {
+          "type": "string"
+        },
+        "tasteIncreasing": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "sanskritName",
+        "gloss",
+        "start",
+        "end",
+        "ayana",
+        "phase",
+        "strength",
+        "tasteIncreasing"
+      ],
+      "type": "object"
+    },
+    "sources": {
+      "items": {
+        "properties": {
+          "chapter": {
+            "type": "string"
+          },
+          "note": {
+            "type": "string"
+          },
+          "publicDomain": {
+            "type": "boolean"
+          },
+          "text": {
+            "type": "string"
+          },
+          "translation": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "verse": {
+            "type": "string"
+          },
+          "year": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "text",
+          "chapter",
+          "verse",
+          "translation",
+          "year",
+          "publicDomain"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "sunrise": {
+      "type": "string"
+    },
+    "sunset": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "sunrise",
+    "sunset",
+    "brahmaMuhurta",
+    "doshaPeriods",
+    "ritu",
+    "doshaCycle",
+    "summary",
+    "sources",
+    "conventions",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already signal read-only and non-destructive behavior, and the description adds useful context: it composes two endpoints into one response, applies default conventions, and echoes those conventions back. There is no contradiction between the description and annotations. The only minor gap is that 'default conventions' and 'those two routes' are not spelled out explicitly, but the read-only safety profile is well covered.

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?

Three dense, front-loaded sentences: the first states the primary output, the second explains the composition value, and the third gives routing alternatives. There is no filler or repetition of schema content. The minor stylistic issue of 'one days' does not affect clarity.

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?

The description names the main output components, explains the composition behavior, and points to alternatives for customization; the input schema fully covers parameter semantics and the output schema covers return-value details. It is complete enough for correct invocation. The indirect reference to 'those two routes' is the only point left to inference.

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?

All six parameters are fully documented in the input schema, so the description does not need to repeat their semantics. The top-level description adds no parameter-level detail beyond what the schema already provides, such as latitude affecting day/night length or timezone defaults. With 100% schema coverage, the baseline score of 3 is appropriate.

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 exactly what the tool returns: one day's Ayurveda reading with sunrise, brahma muhurta, dosha periods, season, and dosha's yearly-cycle position. It also differentiates itself from siblings by explaining that it composes the routine and season routes so a widget needs one call instead of two. This is specific enough to select over get_ayurveda_doshas or the post_* routes.

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?

Explicitly tells the agent when to use this tool: when defaults are acceptable and a single composed response is desired. It also tells the agent when not to use it: call the two route alternatives directly to choose a different season scheme, zodiac, hemisphere, or dosha clock. This is clear, actionable routing guidance.

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

All Ayurveda MCP Server by RoxyAPI 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?