Ayurveda MCP Server by RoxyAPI

List the six tastes - Ayurveda rasa and dosha matrix API

get_ayurveda_tastes

Read-only

Return the six rasas, the tastes of Ayurveda, with the complete eighteen-cell matrix of which taste lowers and raises which dosha, in both directions. The order is the one the root verse gives, which is also the order of strength it states, and it puts bitter before pungent where most modern lists reverse them. The matrix is returned on each taste and again as a per-dosha index, so a caller can read it either way without deriving one from the other.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`limit`	No	Maximum items to return per page. Range: 1-6, default 6.
`offset`	No	Number of items to skip for pagination. Default 0.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`limit`	Yes
`rasas`	Yes
`total`	Yes
`matrix`	Yes
`offset`	Yes
`sources`	Yes
`strengthOrder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "matrix": {
+      "additionalProperties": {
+        "properties": {
+          "decreasedBy": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "increasedBy": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "decreasedBy",
+          "increasedBy"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "meta": {
+      "properties": {
+        "disclaimer": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "disclaimer"
+      ],
+      "type": "object"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "rasas": {
+      "items": {
+        "properties": {
+          "decreases": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "devanagari": {
+            "type": "string"
+          },
+          "elements": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "english": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "increases": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "sanskritName": {
+            "type": "string"
+          },
+          "textForm": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "sanskritName",
+          "devanagari",
+          "textForm",
+          "english",
+          "elements",
+          "decreases",
+          "increases"
+        ],
+        "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"
+    },
+    "strengthOrder": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "strengthOrder",
+    "rasas",
+    "matrix",
+    "sources",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the ordering rationale (root verse, bitter before pungent), the dual representation (per-taste and per-dosha index), and the fact that both are returned without derivation. This goes beyond the annotations and helps the agent understand the response shape.

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, each earning its place: the first states the core content, the second explains the ordering rationale, the third describes the dual matrix representation. Front-loaded with the primary purpose, no wasted words.

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 tool has an output schema, read-only annotations, and 100% schema coverage for parameters. The description adds the ordering context and dual-representation detail that an agent needs to interpret the response correctly. Nothing essential is missing for a read-only list tool.

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 four parameters thoroughly. The description doesn't add parameter-specific details beyond what the schema provides, but it doesn't need to. Baseline 3 is correct when the schema carries the full burden.

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 ('Return') and resource ('the six rasas... with the complete eighteen-cell matrix'), and distinguishes itself from siblings by naming the exact content and ordering. It clearly differentiates from get_ayurveda_doshas and get_ayurveda_qualities by focusing on tastes and the dosha matrix.

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

Usage Guidelines4/5

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

The description implies when to use this tool: when a caller needs the rasa-dosha matrix in both directions, with a specific traditional order. It doesn't explicitly name alternatives or exclusions, but the context signals and sibling list make the use case clear. A 4 is appropriate because it provides clear context without explicit when-not-to-use 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?