AstroWay Astrology API (full catalogue)

Challenge Cycles (kabbalistic-strict)

astroway_numks_challenge

Read-onlyIdempotent

Calculate four Challenge cycles: life-area difficulties to master, derived from birth date components. Numerology: Kabbalistic (Mathers strict) system.

[Group: Numerology: Kabbalistic (Mathers strict)] [Endpoint: POST /v1/numerology/kabbalistic-strict/challenge] [Required: name, date] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_numerology_kabbalistic_strict_challenge.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "astroway_numks_challenge"
  }
}

Input Schema

Name	Required	Description
`date`	Yes
`name`	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.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`system`	No
`challenges`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026

changedOutput schema / properties / challenges / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "first": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "meaning": {
-                "anyOf": [
-                  {
-                    "additionalProperties": {},
-                    "properties": {
-                      "archetype": {
-                        "anyOf": [
-                          {
-                            "type": "string"
-                          },
-                          {
-                            "type": "null"
-                          }
-                        ]
-                      }
-                    },
-                    "type": "object"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "reduced": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "fourth": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "reduced": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "second": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "reduced": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "third": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "reduced": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "first": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "meaning": {
+                "anyOf": [
+                  {
+                    "additionalProperties": {},
+                    "properties": {
+                      "archetype": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      }
+                    },
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "reduced": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "fourth": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "reduced": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "second": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "reduced": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "third": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "reduced": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / system / anyOf

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

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

First observedOct 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds non-obvious operational context: a concrete credit cost and tier, the POST endpoint, and the fact that the tool is an alias — which affects agent-side tool selection and budgeting. It does not describe output shape, but an output schema exists.

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?

Short and front-loaded: the purpose sentence comes first, followed by scannable bracketed metadata lines for group, endpoint, required fields and cost. The only mild redundancy is repeating the required parameters already present in the schema's required array, and the alias note is arguably necessary context rather than waste.

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?

Since an output schema exists, return values need not be explained, and cost/endpoint/required inputs are supplied. However, for a tool embedded among ~20 near-identical numerology siblings, the definition lacks the disambiguation and minimal input semantics (e.g., date validity rules, how 'name' is used in a Kabbalistic calculation) that would let an agent choose and call it confidently without opening the schema.

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 50%: 'fields' and 'precision' are well documented in the schema, while 'name' and 'date' rely on constraints (pattern, min/maxLength) rather than prose. The description only restates that name and date are required and hints that output derives from 'birth date components' — it adds no format, timezone, or name-handling semantics beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Calculate four Challenge cycles: life-area difficulties to master, derived from birth date components,' plus the exact numerological system (Kabbalistic/Mathers strict). It also discloses that it is a cursor-friendly alias of astroway_numerology_kabbalistic_strict_challenge, which prevents duplicate-call confusion. It stops short of explaining how 'challenge' differs from the many sibling systems (Chaldean/Pythagorean/Vedic challenge, or Kabbalistic-strict pinnacles) beyond the system label.

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: the caller infers they should invoke it when they want challenge cycles in the strict Kabbalistic system. There is no explicit when-to-use / when-not-to-use statement and no routing to alternatives such as astroway_numerology_kabbalistic_challenge or astroway_numks_pinnacles. The [Required: name, date] and [Cost: 10 credits (Tier 1)] lines give practical prerequisites but not selection guidance.

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?