Skip to main content
Glama

Ayurveda MCP Server by RoxyAPI

by com.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
NameRequiredDescriptionDefault
dateNoReading 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.
langNoResponse 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
compactNoSet 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.
latitudeNoLatitude in decimal degrees. It sets how long the day and the night actually are, which is what the dosha periods are cut from.
timezoneNoSelects 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").
longitudeNoLongitude in decimal degrees. It sets the clock time of sunrise at this place.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already covered. The description adds meaningful behavioral detail: it composes two routes, defaults apply throughout and are echoed, and it mentions that dosha periods are 'cut from the actual day and night.' This goes beyond what annotations provide.

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 sentences, front-loaded with the output list, and every sentence earns its place: what it returns, why to use it, and when to avoid it. No fluff or repetition.

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?

No output schema exists, so the description carries the burden of describing the return value. It lists the key components of the reading and notes the composition behavior, which is sufficient for a widget-oriented tool. Minor gaps like response structure details are acceptable given the compact parameter description.

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%, so the schema already documents all six parameters. The description does not need to add parameter-level details, and it does not introduce any conflicting parameter context. Baseline 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?

The description states a specific verb ('Get'), a concrete resource ('one days Ayurveda reading for a place'), and enumerates the exact outputs: sunrise, brahma muhurta window, six dosha periods, and season. It also explains that this route composes two other routes, clearly distinguishing it from sibling tools without explicitly naming them.

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 tells the agent when to use this tool ('so a widget needs one call rather than two') and explicitly states the exception: 'call those two routes directly to choose a different season scheme, zodiac, hemisphere or dosha clock.' This is actionable routing guidance that prevents misuse.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools are sharply separated by resource: dosha list/detail, qualities, tastes, constitution, routine, and season. The overlap is get_ayurveda_daily, which deliberately combines dinacharya and ritucharya, but its description clearly frames it as a one-call convenience and points to the post routes for customised calls.

Naming Consistency5/5

All tool names follow the same verb_ayurveda_resource pattern, with get_ for read-only catalogue lookups and post_ for calculations. This makes the API predictable; the only minor oddity is doshas_id, but it does not break the pattern.

Tool Count5/5

Eight tools cover the core catalogue (doshas, qualities, tastes), daily/seasonal readings, and the two calculation endpoints. This is well-scoped and each tool earns its place without redundancy.

Completeness4/5

The surface covers the main Ayurveda knowledge objects and the key date/location calculations, so agents can assemble useful readings. The main gap is that there is no separate endpoint for managing or listing location/convention options, but the daily composite helps tie the routes together.

Resources