Kabbalah MCP Server by RoxyAPI

Compare two names - gematria name compatibility API with every component published

post_kabbalah_compatibility

Read-only

Score two names against each other in gematria and return both profiles, the ciphers they agree on, and a composite with every component and its maximum published beside it. Equal value under the standard reading is the one relation the classical method actually works with and it carries the largest weight; the rest of the composite is ours and the response says so, so a caller can recompute or ignore it. Built for name compatibility features, relationship content and any product that wants a number it can show the arithmetic for.

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
`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.
`firstName`	No	First name in Latin script. Send firstNameHebrew instead to control the spelling.
`secondName`	No	Second name in Latin script. Send secondNameHebrew instead to control the spelling.
`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
`firstNameHebrew`	No	First name already in Hebrew, which skips the transliteration step.
`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
`secondNameHebrew`	No	Second name already in Hebrew, which skips the transliteration step.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`band`	Yes
`first`	Yes
`score`	Yes
`second`	Yes
`reading`	Yes
`components`	Yes
`conventions`	Yes
`sharedValues`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "band": {
+      "type": "string"
+    },
+    "components": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "matched": {
+            "type": "boolean"
+          },
+          "maximum": {
+            "type": "number"
+          },
+          "points": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "points",
+          "maximum",
+          "matched"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "conventions": {
+      "properties": {
+        "misparGadol": {
+          "type": "string"
+        },
+        "transliteration": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "misparGadol"
+      ],
+      "type": "object"
+    },
+    "first": {
+      "properties": {
+        "hebrew": {
+          "type": "string"
+        },
+        "input": {
+          "type": "string"
+        },
+        "reduced": {
+          "type": "number"
+        },
+        "romanization": {
+          "type": "string"
+        },
+        "rule": {
+          "type": "string"
+        },
+        "sephirah": {
+          "type": "string"
+        },
+        "sephirahEnglish": {
+          "type": "string"
+        },
+        "standard": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "input",
+        "hebrew",
+        "romanization",
+        "rule",
+        "standard",
+        "reduced",
+        "sephirah",
+        "sephirahEnglish"
+      ],
+      "type": "object"
+    },
+    "reading": {
+      "type": "string"
+    },
+    "score": {
+      "type": "number"
+    },
+    "second": {
+      "properties": {
+        "hebrew": {
+          "type": "string"
+        },
+        "input": {
+          "type": "string"
+        },
+        "reduced": {
+          "type": "number"
+        },
+        "romanization": {
+          "type": "string"
+        },
+        "rule": {
+          "type": "string"
+        },
+        "sephirah": {
+          "type": "string"
+        },
+        "sephirahEnglish": {
+          "type": "string"
+        },
+        "standard": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "input",
+        "hebrew",
+        "romanization",
+        "rule",
+        "standard",
+        "reduced",
+        "sephirah",
+        "sephirahEnglish"
+      ],
+      "type": "object"
+    },
+    "sharedValues": {
+      "items": {
+        "properties": {
+          "cipher": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "value": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "cipher",
+          "name",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "first",
+    "second",
+    "sharedValues",
+    "score",
+    "band",
+    "components",
+    "reading",
+    "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

A4.3/5.0

Behavior5/5

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

Beyond the readOnly and non-destructive annotations, the description discloses how the composite works: the standard equal-value relation carries the largest weight, the rest is proprietary, and the response explicitly says so so callers can recompute or ignore it. This gives agents an unusually clear picture of the algorithm's provenance and limits.

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 front-loaded with the core function, followed by the weighting caveat and then the target use cases. It is a little dense, particularly the middle sentence about standard reading and composite ownership, but every sentence carries distinct information and there is no filler.

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?

The description conveys the tool's purpose, output shape, algorithmic transparency, and use cases, while the output schema and fully documented parameters cover invocation details. It is complete enough for correct selection and calling, though it does not offer guidance on edge cases such as mixing Hebrew and Latin inputs, which the schema leaves open.

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?

The input schema has 100% parameter documentation with detailed descriptions for lang, compact, firstName, secondName, and transliteration. The main description adds general context about comparing two names, but it does not add meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Score'), a clear resource ('two names against each other in gematria'), and the exact output components: both profiles, ciphers they agree on, and a composite. This separates it from siblings like post_kabbalah_gematria and get_kabbalah_names, which handle single names or cipher lookup rather than pairwise compatibility.

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 gives clear intended contexts: 'name compatibility features, relationship content and any product that wants a number it can show the arithmetic for.' It does not explicitly name sibling tools as alternatives or say when not to use them, but the use-case framing is enough to guide selection.

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?