Kabbalah MCP Server by RoxyAPI

List the 72 names - Shem HaMephorash API derived from the verses

get_kabbalah_names

Read-only

Return the seventy two names, each with the three letters it is read from, the divine name suffix, the five degree ecliptic arc it governs, the sign that arc falls in and the angelic choir it belongs to. The names are DERIVED from three verses of Exodus read in the boustrophedon order rather than copied from a table, and any row where a named published list differs is flagged on that row. Pass a longitude to get the single name governing that degree. Built for birth angel features, Shem HaMephorash reference pages and any product that has to show where a name comes from.

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
`limit`	No	Maximum items to return per page. Range: 1-72, default 20.
`offset`	No	Number of items to skip for pagination. Default 0.
`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.
`longitude`	No	Ecliptic longitude in degrees, 0 inclusive to 360 exclusive, measured from 0 Aries. Returns the single name governing that degree instead of the list. 360 is rejected because it is the same point as 0 and the arcs are half open at the top.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`names`	Yes
`total`	Yes
`offset`	Yes
`longitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026
- addedInput schema / properties / longitude / minimum
```
Added value: +0
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed5 schema fields changedSep 20, 2026
- removedInput schema / properties / longitude / minimum
```
Removed value: -0
```
- changedInput schema / properties / longitude / type
```
Previous value: -[
-  "number",
-  "null"
-]New value: +"number"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "longitude": {
+      "type": "number"
+    },
+    "names": {
+      "items": {
+        "properties": {
+          "arcEnd": {
+            "type": "number"
+          },
+          "arcStart": {
+            "type": "number"
+          },
+          "choir": {
+            "type": "string"
+          },
+          "degreeInSign": {
+            "type": "number"
+          },
+          "letters": {
+            "type": "string"
+          },
+          "lettersAsWritten": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "publishedDisagreement": {
+            "properties": {
+              "list": {
+                "type": "string"
+              },
+              "prints": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "list",
+              "prints"
+            ],
+            "type": "object"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "suffix": {
+            "type": "string"
+          },
+          "traditionalName": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "letters",
+          "lettersAsWritten",
+          "suffix",
+          "name",
+          "romanization",
+          "traditionalName",
+          "arcStart",
+          "arcEnd",
+          "sign",
+          "degreeInSign",
+          "choir"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "names"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description goes beyond the readOnly/destructive annotations by explaining that the names are 'DERIVED from three verses of Exodus read in the boustrophedon order rather than copied from a table' and that discrepant rows are flagged. This adds meaningful behavioral context about data provenance and flags, with no contradiction to 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 front-loads the core output and then adds details on derivation, longitude mode, and use cases. It is a bit dense but every sentence contributes useful information, so it earns a score above average.

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?

Given the rich input schema and an output schema, the description provides essential conceptual background, derivation methodology, and intended use cases. It does not need to spell out return values because an output schema exists, and it covers the key behavioral variant (longitude). It is complete enough for an agent to select and invoke correctly.

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 parameters are documented in the schema. The description adds little beyond the schema for parameters, mentioning longitude behavior in prose but not adding new semantic detail. Per the rubric, a baseline 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 clearly states a specific verb and resource: 'Return the seventy two names' with a detailed list of attributes: letters, divine name suffix, ecliptic arc, sign, and angelic choir. It also mentions the alternative single-name behavior via longitude, which distinguishes it from sibling tools like get_kabbalah_names_number or get_kabbalah_letters.

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?

It provides clear context for when to use the tool ('Built for birth angel features, Shem HaMephorash reference pages...') and describes the conditional longitude mode ('Pass a longitude to get the single name governing that degree'). However, it does not explicitly name alternative tools or state when not to use it, so it falls short of 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?