Numerology MCP Server by RoxyAPI

Calculate Chaldean numerology - Chaldean name number calculator API

post_numerology_chaldean

Read-only

Calculate a complete Chaldean numerology reading for a name, following Cheiro. The Destiny or name number, the Soul Urge from the vowels and the Personality from the consonants each come with the compound number from 10 to 52, the single-digit root and the classical compound interpretation, and a longer name is read name by name with every step shown in its calculation. The response adds the planetary ruler and meaning of the Destiny root, a caution flag for the roots 4 and 8, and a summary, in the language set by lang. Built for Chaldean numerology calculators, name analysis tools and AI agents.

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
`name`	Yes	The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name. It needs at least one vowel (A, E, I, O, U) and one consonant, since the Soul Urge is read from the vowels and the Personality from the consonants; Y counts as a consonant. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.
`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
`name`	Yes
`caution`	Yes
`destiny`	Yes
`summary`	Yes
`soulUrge`	Yes
`personality`	Yes
`numberMeaning`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / name / description

Previous value: -"The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name."New value: +"The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name. It needs at least one vowel (A, E, I, O, U) and one consonant, since the Soul Urge is read from the vowels and the Personality from the consonants; Y counts as a consonant. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "caution": {
+      "type": "boolean"
+    },
+    "destiny": {
+      "properties": {
+        "calculation": {
+          "type": "string"
+        },
+        "compound": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "compoundMeaning": {
+          "properties": {
+            "meaning": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "nature": {
+              "enum": [
+                "fortunate",
+                "unfortunate",
+                "mixed"
+              ],
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            },
+            "sameAs": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "number",
+            "name",
+            "nature",
+            "meaning"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "root": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "compound",
+        "root",
+        "calculation",
+        "compoundMeaning"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "numberMeaning": {
+      "properties": {
+        "caution": {
+          "type": "boolean"
+        },
+        "keywords": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "planet": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "planet",
+        "title",
+        "keywords",
+        "caution",
+        "meaning"
+      ],
+      "type": "object"
+    },
+    "personality": {
+      "properties": {
+        "calculation": {
+          "type": "string"
+        },
+        "compound": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "compoundMeaning": {
+          "properties": {
+            "meaning": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "nature": {
+              "enum": [
+                "fortunate",
+                "unfortunate",
+                "mixed"
+              ],
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            },
+            "sameAs": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "number",
+            "name",
+            "nature",
+            "meaning"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "root": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "compound",
+        "root",
+        "calculation",
+        "compoundMeaning"
+      ],
+      "type": "object"
+    },
+    "soulUrge": {
+      "properties": {
+        "calculation": {
+          "type": "string"
+        },
+        "compound": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "compoundMeaning": {
+          "properties": {
+            "meaning": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "nature": {
+              "enum": [
+                "fortunate",
+                "unfortunate",
+                "mixed"
+              ],
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            },
+            "sameAs": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "number",
+            "name",
+            "nature",
+            "meaning"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "root": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "compound",
+        "root",
+        "calculation",
+        "compoundMeaning"
+      ],
+      "type": "object"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "destiny",
+    "soulUrge",
+    "personality",
+    "numberMeaning",
+    "caution",
+    "summary"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Helen"
+  }
+]

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 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=true and destructiveHint=false, so the safety profile is covered. The description nonetheless adds real behavioral context: the compound range 10-52, name-by-name reading with each step shown, a caution flag for roots 4 and 8, script-to-Latin normalisation, and language-dependent output. It does not describe latency, rate limits, or error behavior.

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 verb-and-resource lead is front-loaded and the output inventory is packed efficiently into two sentences. The closing 'Built for Chaldean numerology calculators, name analysis tools and AI agents' is audience marketing that does not help an agent decide or call, so it is not fully waste-free.

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?

With an output schema present, the description need not enumerate returns, yet it summarizes the reading's contents and its language dependence, and the 100%-covered schema handles parameters. The only meaningful gap is guidance on choosing this tool over the overlapping single-aspect 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 description coverage is 100%, so all three parameters are fully documented in the schema (including the detailed name-script rules and compact columnar shape). The description adds only a light restatement via 'in the language set by lang', so the baseline 3 applies.

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 (Calculate) and resource (complete Chaldean numerology reading for a name), and the Cheiro/Chaldean qualifier differentiates it from the many Pythagorean-style siblings like post_numerology_soul_urge and post_numerology_personality. It stops short of naming an alternative, so an agent must infer sibling routing from the tradition label alone.

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 through the scope: this is the complete-reading tool, useful when the whole Destiny/Soul Urge/Personality bundle is wanted. There is no explicit when-to-use, no when-not-to-use, and no pointer to the narrower single-aspect siblings that produce overlapping values, leaving the selection to inference.

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

All Numerology 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?