AstroWay Astrology API (full catalogue)

Birthday (kabbalistic-strict)

astroway_numerology_kabbalistic_strict_birthday

Read-onlyIdempotent

Calculate the Birthday number from the day-of-birth digit. Numerology: Kabbalistic (Mathers strict) system.

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

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
`date`	No
`name`	No
`system`	No
`birthday`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 7, 2026

changedOutput schema / properties / birthday / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "isMaster": {
-        "anyOf": [
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "meaning": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "properties": {
-              "archetype": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "number": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "shortRead": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              },
-              "strengths": {
-                "anyOf": [
-                  {
-                    "items": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ]
-                    },
-                    "type": "array"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ]
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "raw": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "reduced": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "steps": {
-        "anyOf": [
-          {
-            "items": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "isMaster": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "meaning": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "archetype": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "number": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "shortRead": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "strengths": {
+                "anyOf": [
+                  {
+                    "items": {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "raw": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "reduced": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "steps": {
+        "anyOf": [
+          {
+            "items": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / date / anyOf

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

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

removedOutput schema / properties / name / anyOf

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

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "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

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the POST endpoint, the mandatory parameter set, and a concrete cost of 10 credits (Tier 1), which lets an agent reason about budget before calling.

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 core purpose is front-loaded in one sentence, followed by scannable bracketed metadata. The group label largely repeats the system name already in sentence two, but overall the definition is tight and efficiently structured.

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 cost/endpoint are supplied. What is missing is the substantive meaning of "strict" versus the standard Kabbalistic variant and any error or date-format behavior, which matters for a computational tool with near-identical siblings.

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 coverage is 50%: `fields` and `precision` are documented, while `name` and `date` are bare. The description partially compensates by naming them as required and implying `date` supplies the day-of-birth digit, but it never explains why `name` is required for a number derived only from the birth day — a genuine ambiguity left unresolved.

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?

The description states a specific verb and resource ("Calculate the Birthday number from the day-of-birth digit") and pins the system as Kabbalistic (Mathers strict). It does not, however, explain how this differs from the sibling astroway_numerology_kabbalistic_birthday (non-strict), which is the one distinction an agent actually needs to make here.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over the other eleven birthday-number siblings (Chaldean, Pythagorean, Vedic, non-strict Kabbalistic), nor any exclusion or prerequisite beyond the terse "Required: name, date". The agent must infer selection purely from the system name embedded in the tool name.

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?