Kabbalah MCP Server by RoxyAPI

Generate a name profile - Kabbalah name numerology API with the spelling shown

post_kabbalah_name_profile

Read-only

Score a name across the rabbinic gematria ciphers and place it on the Tree of Life, with every candidate Hebrew spelling shown and the chosen one named. The response carries the standard, the large, the small and the preceding readings with the per letter breakdown, the sephirah the reduced value points at, and the curated words that share the value. Built for name meaning pages, Kabbalah numerology features and any product that wants a name reading it can defend line by line.

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`	No	The name in Latin script, to be written in Hebrew and then scored. Non Latin scripts are folded to Latin first. Send nameHebrew instead to control the spelling yourself.
`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.
`nameHebrew`	No	The name already in Hebrew, which skips the transliteration step entirely and scores exactly the spelling you sent.
`misparGadol`	No	Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.	finals-500-900
`transliteration`	No	How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.	letter-map-mathers

Output Schema

TableJSON Schema

Name	Required	Description	Default
`input`	Yes
`chosen`	Yes
`values`	Yes
`letters`	Yes
`matches`	Yes
`sephirah`	Yes
`conventions`	Yes
`hebrewForms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "chosen": {
+      "properties": {
+        "hebrew": {
+          "type": "string"
+        },
+        "romanization": {
+          "type": "string"
+        },
+        "rule": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "hebrew",
+        "romanization",
+        "rule"
+      ],
+      "type": "object"
+    },
+    "conventions": {
+      "properties": {
+        "misparGadol": {
+          "type": "string"
+        },
+        "transliteration": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "misparGadol"
+      ],
+      "type": "object"
+    },
+    "hebrewForms": {
+      "items": {
+        "properties": {
+          "hebrew": {
+            "type": "string"
+          },
+          "letters": {
+            "items": {
+              "properties": {
+                "glyph": {
+                  "type": "string"
+                },
+                "isFinal": {
+                  "type": "boolean"
+                },
+                "letterId": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "value": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "glyph",
+                "letterId",
+                "name",
+                "isFinal",
+                "value"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "rule": {
+            "type": "string"
+          },
+          "values": {
+            "items": {
+              "properties": {
+                "alternateValues": {
+                  "items": {
+                    "type": "number"
+                  },
+                  "type": "array"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "source": {
+                  "type": "string"
+                },
+                "tradition": {
+                  "type": "string"
+                },
+                "value": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "id",
+                "value",
+                "tradition",
+                "source"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "hebrew",
+          "romanization",
+          "rule",
+          "values",
+          "letters"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "input": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "nameHebrew": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "letters": {
+      "items": {
+        "properties": {
+          "glyph": {
+            "type": "string"
+          },
+          "isFinal": {
+            "type": "boolean"
+          },
+          "letterId": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "glyph",
+          "letterId",
+          "name",
+          "isFinal",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "matches": {
+      "items": {
+        "properties": {
+          "hebrew": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "note": {
+            "type": "string"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "sources": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "hebrew",
+          "romanization",
+          "meaning",
+          "value",
+          "note",
+          "sources"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sephirah": {
+      "properties": {
+        "english": {
+          "type": "string"
+        },
+        "hebrew": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "number": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "reading": {
+          "type": "string"
+        },
+        "reduced": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "english",
+        "hebrew",
+        "reduced",
+        "meaning",
+        "reading"
+      ],
+      "type": "object"
+    },
+    "values": {
+      "properties": {
+        "large": {
+          "type": "number"
+        },
+        "preceding": {
+          "type": "number"
+        },
+        "small": {
+          "type": "number"
+        },
+        "standard": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "standard",
+        "large",
+        "small",
+        "preceding"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "input",
+    "hebrewForms",
+    "chosen",
+    "values",
+    "letters",
+    "sephirah",
+    "matches",
+    "conventions"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 16, 2026

changedInput schema / properties / transliteration / description

Previous value: -"How a Latin name is written in Hebrew before it is scored. One member, a deterministic published letter map. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction, and every published Hebrew standard romanizes the other way. Send textHebrew to control the spelling yourself."New value: +"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction."

changedInput schema / properties / transliteration / enum

Previous value: -[
-  "letter-map-mathers"
-]New value: +[
+  "letter-map-mathers",
+  "letter-map-modern"
+]

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail beyond the annotations: it promises 'every candidate Hebrew spelling shown and the chosen one named' and enumerates exactly what the response carries (standard, large, small, preceding readings, per-letter breakdown, sephirah, curated words). This gives an agent a concrete picture of the tool's output behavior without contradicting the annotations.

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 description is two dense sentences that pack in the core action, the unique spelling behavior, the full response contents, and the intended use cases. It is front-loaded with the primary function and then fills in supporting details. It is slightly longer than absolute minimum but every clause earns its place, so it remains well-structured.

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 and fully documented parameters, the description does not need to explain return values or parameter syntax. It supplies the missing context: the tool's purpose, the product fit, and the key behavioral promise about Hebrew spelling. The only minor gap is that it does not discuss how to orchestrate the optional name/nameHebrew parameters, but the schema already hints at this, so the description is complete enough for correct invocation.

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 the input schema fully documents all six parameters, including enums and mutually exclusive hints (e.g., 'Send nameHebrew instead to control the spelling yourself'). The tool description itself adds no parameter-level meaning, so the baseline of 3 applies; it neither improves nor detracts from what the schema already provides.

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 clearly states the tool's core action: 'Score a name across the rabbinic gematria ciphers and place it on the Tree of Life,' along with distinctive details like 'every candidate Hebrew spelling shown' and the full response breakdown. This is specific enough to identify the tool's function, but it does not explicitly differentiate from close siblings like post_kabbalah_gematria or post_kabbalah_birth_profile, so it only partially distinguishes.

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

Usage Guidelines4/5

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

The description provides clear usage context: 'Built for name meaning pages, Kabbalah numerology features and any product that wants a name reading it can defend line by line.' This tells an agent when to reach for this tool, but it offers no exclusions or alternatives, so it stops short of the explicit when/when-not guidance that would merit a 5.

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

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