Ayurveda MCP Server by RoxyAPI

List the twenty qualities - Ayurveda guna pairs API

get_ayurveda_qualities

Read-only

Return the twenty gunas, the qualities of Ayurveda, as the ten opposed pairs the commentaries spell out, each member with the single action word attached to it, and the half-verse that states the like-increases-like rule the whole domain runs on. Each quality carries the doshas that hold it, so the pairs join straight to the dosha catalogue. One pair carries a recorded disagreement between the two commentaries, and the response states it rather than resolving it silently, because the choice decides which dosha that pair joins to.

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-10, default 10.
`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
`rule`	Yes
`limit`	Yes
`pairs`	Yes
`total`	Yes
`offset`	Yes
`sources`	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"
+    },
+    "meta": {
+      "properties": {
+        "disclaimer": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "disclaimer"
+      ],
+      "type": "object"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "pairs": {
+      "items": {
+        "properties": {
+          "a": {
+            "properties": {
+              "action": {
+                "type": "string"
+              },
+              "actionSanskrit": {
+                "type": "string"
+              },
+              "doshas": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "english": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "sanskritName": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "sanskritName",
+              "english",
+              "action",
+              "actionSanskrit",
+              "doshas"
+            ],
+            "type": "object"
+          },
+          "b": {
+            "properties": {
+              "action": {
+                "type": "string"
+              },
+              "actionSanskrit": {
+                "type": "string"
+              },
+              "doshas": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "english": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "sanskritName": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "sanskritName",
+              "english",
+              "action",
+              "actionSanskrit",
+              "doshas"
+            ],
+            "type": "object"
+          },
+          "note": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "number",
+          "a",
+          "b"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rule": {
+      "type": "string"
+    },
+    "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"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "rule",
+    "pairs",
+    "sources",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important non-obvious behavior: one pair carries a recorded disagreement between commentaries and the response 'states it rather than resolving it silently,' because it determines dosha linkage. It also explains that qualities carry doshas and the governing rule, adding real context the annotations do not provide.

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 dense but front-loaded with the core action and all sentences carry substantive information. Some clauses are ornate, but nothing is filler or redundant with the schema.

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?

With an output schema present and all parameters documented in the input schema, the description fills the remaining contextual gaps: content structure, paired organization, dosha linkage, and the special handling of a disputed pair. Nothing an agent needs to call this correctly is missing.

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 fully documents lang, limit, offset, and compact. The description adds no additional parameter-level meaning, making the baseline 3 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 names a specific verb and resource: 'Return the twenty gunas' as ten opposed pairs with action words and a half-verse rule. This clearly distinguishes the tool from sibling tools like get_ayurveda_doshas and get_ayurveda_tastes by its unique content and structure.

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 implies the tool is for retrieving the twenty Ayurvedic qualities but never explicitly states when to choose it over alternatives or when not to use it. The domain-level content makes the niche inferable, but there are no exclusions or direct comparisons to sibling tools.

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?