Ayurveda MCP Server by RoxyAPI

Dinacharya daily routine - Brahma muhurta and dosha clock API

post_ayurveda_dinacharya

Read-only

Compute the dinacharya daily routine for one date and one place: sunrise, sunset, the brahma muhurta window, and the six dosha periods of the day and the night. The default division cuts the actual day and the actual night into thirds, which is what the frame chapter states, and the modern clock grid is returned alongside it under its own label so a caller can show either. The brahma muhurta is a fixed window of 96 to 48 minutes before sunrise rather than a share of the night, which is the reading the classical commentary settles on.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	The local calendar date, in YYYY-MM-DD format. Sunrise and sunset are computed for this date at the given place, and the whole routine follows from them, so the answer changes through the year at any latitude away from the equator.
`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 the whole difference between this and a printed timetable: at 51 north in June the day runs about sixteen and a half hours and its thirds are five and a half hours each.
`timezone`	No	Timezone as an IANA name such as "Europe/London", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the requested date. It decides which local day is meant and, on the clock-hour grid, where the blocks fall. Defaults to 0.
`longitude`	Yes	Longitude in decimal degrees. It sets the clock time of sunrise at this place.
`doshaClock`	No	How the six dosha periods are cut. "sunrise-anchored" divides the actual day and the actual night at this place into thirds, which is the division the frame chapter states, and is the default. "clock-hours" is the modern grid of six four-hour blocks from six in the morning; no classical text assigns clock hours, and the grid is only exact at an equinox near the equator. Both sets are returned whichever is chosen, so a caller can show one and reconcile against the other.	sunrise-anchored

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`meta`	Yes
`sunset`	Yes
`routine`	Yes
`sources`	Yes
`summary`	Yes
`sunrise`	Yes
`conventions`	Yes
`nextSunrise`	Yes
`doshaPeriods`	Yes
`brahmaMuhurta`	Yes
`alternatePeriods`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "alternatePeriods": {
+      "items": {
+        "properties": {
+          "dosha": {
+            "type": "string"
+          },
+          "end": {
+            "type": "string"
+          },
+          "span": {
+            "type": "string"
+          },
+          "start": {
+            "type": "string"
+          },
+          "third": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "dosha",
+          "start",
+          "end",
+          "span"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "brahmaMuhurta": {
+      "properties": {
+        "end": {
+          "type": "string"
+        },
+        "muhurtaMinutes": {
+          "type": "number"
+        },
+        "muhurtasPerAhoratra": {
+          "type": "number"
+        },
+        "source": {
+          "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"
+        },
+        "start": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "start",
+        "end",
+        "muhurtaMinutes",
+        "muhurtasPerAhoratra",
+        "source"
+      ],
+      "type": "object"
+    },
+    "conventions": {
+      "properties": {
+        "doshaClock": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "doshaClock"
+      ],
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "doshaPeriods": {
+      "items": {
+        "properties": {
+          "dosha": {
+            "type": "string"
+          },
+          "end": {
+            "type": "string"
+          },
+          "span": {
+            "type": "string"
+          },
+          "start": {
+            "type": "string"
+          },
+          "third": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "dosha",
+          "start",
+          "end",
+          "span"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "properties": {
+        "disclaimer": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "disclaimer"
+      ],
+      "type": "object"
+    },
+    "nextSunrise": {
+      "type": "string"
+    },
+    "routine": {
+      "items": {
+        "properties": {
+          "guidance": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "order": {
+            "type": "number"
+          },
+          "sanskritName": {
+            "type": "string"
+          },
+          "source": {
+            "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"
+          },
+          "timing": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "order",
+          "id",
+          "sanskritName",
+          "guidance",
+          "timing",
+          "source"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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",
+    "nextSunrise",
+    "brahmaMuhurta",
+    "doshaPeriods",
+    "alternatePeriods",
+    "routine",
+    "summary",
+    "sources",
+    "conventions",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds valuable behavioral context: the default division cuts actual day and night into thirds, the modern clock grid is returned alongside by default so a caller can show either, both sets are returned whichever doshaClock option is chosen, and the brahma muhurta is a fixed 96-to-48-minute pre-sunrise window. This goes beyond the annotations without contradicting them.

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 tight and front-loaded; all three sentences add meaningful computation semantics. It is on the slightly dense side, but not redundant, so it remains well-structured rather than maximally concise.

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

Completeness5/5

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

The description is complete for this tool's complexity: it explains the core computation, the two division schemes, the brahma muhurta detail, and the fact that both result sets are returned. The output schema covers return structure, and the annotations cover safety, leaving no critical gap for correct invocation.

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 100 percent, so the baseline of 3 applies. The description adds useful interpretive context about the division method and the brahma muhurta window, but it does not materially supplement the already thorough parameter descriptions in the schema.

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 states a clear action and resource: compute the dinacharya daily routine for one date and one place, enumerating the exact outputs sunrise, sunset, brahma muhurta, and six dosha periods. It is specific enough to be understood, but it does not explicitly differentiate itself from siblings like get_ayurveda_daily or get_ayurveda_doshas, so it stops short of full sibling distinction.

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 intended use is implied by the first sentence: this is the tool for a date-and-place-specific dinacharya computation. There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the sibling tools, so an agent must infer the selection boundary rather than being told it.

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?