AstroWay Astrology API (full catalogue)

Doshas: KP Kemadruma

astroway_vedic_doshas_kp_kemadruma

Read-onlyIdempotent

Kemadruma yoga: no planet (excl. Sun, Rahu, Ketu) in 2nd or 12th from Moon. Moon-isolation flag, emotional/financial volatility indicator. KP Moon sub-lord chain attached.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/kp/kemadruma] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`dosha`	No
`school`	No
`details`	No
`present`	No
`moonSign`	No
`lagnaSign`	No
`disclaimer`	No
`kpMoonChain`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedNov 7, 2026

removedInput schema / properties / ayanamsaId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / details / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / details / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / disclaimer / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / disclaimer / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / dosha / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / dosha / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / kpMoonChain / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "longitude": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "positionInSign": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "positionInStar": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sign": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "signLord": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "signLordName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "signName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "star": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "starLord": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "starLordName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "starName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sub": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "subName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "subSub": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "subSubName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "longitude": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "positionInSign": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "positionInStar": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "sign": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "signLord": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "signLordName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "signName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "star": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "starLord": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "starLordName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "starName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sub": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "subName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "subSub": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "subSubName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / lagnaSign / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lagnaSign / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / moonSign / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / moonSign / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / present / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / present / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / school / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / school / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add operational context; it adds the credit cost, tier, endpoint, and the fact that a KP Moon sub-lord chain is attached to the result. It does not mention whether the ayanamsa choice changes the verdict or which school KP expects, which is the one behavioral nuance that materially affects correctness.

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 definition sentence is front-loaded and dense with real information, followed by a compact bracketed metadata block that costs almost no tokens. No sentence is wasted; the only mild weakness is that the metadata block is formatted like internal API documentation rather than agent guidance.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the description correctly signals the Moon sub-lord chain is included. However, for a 15-parameter chart tool whose sibling is a full dosha scan, it omits the ayanamsa expectation that makes a KP result meaningful and gives no sizing guidance for the compact-mode response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% across 15 parameters, so the description needs to compensate, and instead it merely repeats the four required fields already listed in the schema's required array. It says nothing about the KP-critical ayanamsa selection (krishnamurti/kp), the timezone versus timezoneOffset precedence, or the compact-mode fields/precision parameters for a large response.

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?

It names the exact technique (Kemadruma yoga) and defines the classical condition precisely — no planet other than Sun/Rahu/Ketu in the 2nd or 12th from the Moon — plus the interpretive label (Moon-isolation, emotional/financial volatility). That is far more specific than a restated title, and the single-dosha scope implicitly separates it from astroway_vedic_doshas_kp_full, though no sibling is named outright.

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?

Usage is only implied: an agent can infer this tool applies when checking Moon isolation specifically, and the cost line (20 credits, Tier 2) hints that the whole-dosha endpoint would be heavier. There is no explicit when-to-use or when-not guidance, and no pointer to astroway_vedic_doshas_kp_full for a broader sweep or to compatibility_dosha_cancellation for cancellation analysis.

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

All AstroWay Astrology API (full catalogue) 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?