AstroWay Astrology API (full catalogue)

Personal Year (kabbalistic)

astroway_numk_personal_year

Read-onlyIdempotent

Calculate the Personal Year number for a given calendar year: the 9-year cycle of personal evolution. Numerology: Kabbalistic (phonetic) system.

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

(Cursor-friendly alias for astroway_numerology_kabbalistic_personal_year.)

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_numk_personal_year"
  }
}

Input Schema

Name	Required	Description
`date`	Yes
`name`	Yes
`year`	No	Calendar year to read. Defaults to the current year (UTC).
`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
`personalYear`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 7, 2026

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"
+]
```

changedOutput schema / properties / personalYear / 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 / system / anyOf

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

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

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / year / description

Added value: +"Calendar year to read. Defaults to the current year (UTC)."

changedInput schema / required

Previous value: -[
-  "name",
-  "date",
-  "year"
-]New value: +[
+  "name",
+  "date"
+]

First observedOct 5, 2026

TDQS

A3.7/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 safety is covered. The description adds genuinely new operational context: a cost of 10 credits (Tier 1), the POST endpoint, and the required-parameter set. It does not mention rate limits or error behavior, so it falls short of a 5.

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 purpose sentence is front-loaded and the metadata lines (group, endpoint, required, cost, alias) are scannable and cheap. There is mild redundancy repeating 'Kabbalistic (phonetic)' in both the prose and the group tag, but no wasted sentences.

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

Completeness4/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 explained, and the description covers cost, endpoint, required inputs, and alias identity. What is missing is the differentiator against the many near-identical personal-year siblings and the semantics of name/date, which matters given 5 parameters at 60% coverage.

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 60%: year, fields, and precision are documented in-schema, while date and name have no schema descriptions. The description only restates '[Required: name, date]', adding no guidance on expected name form (full birth name vs. common name) or how date is used relative to year. That is minimal compensation, so baseline 3 fits.

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 gives a specific verb and resource ('Calculate the Personal Year number'), names the scope ('for a given calendar year'), and pins the system ('Kabbalistic (phonetic)'). It also reveals that this is an alias of astroway_numerology_kabbalistic_personal_year, but it never distinguishes itself from the close siblings astroway_numks_personal_year or astroway_numerology_kabbalistic_strict_personal_year.

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 implied rather than stated: the '9-year cycle' line hints at forecasting use, and 'Cursor-friendly alias' implies it is a drop-in for the canonical tool. There is no explicit when-to-use/when-not guidance, and no rule telling the agent to prefer this alias over the identically-purposed Kabbalistic, strict, or numks personal-year tools.

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?