Kabbalah MCP Server by RoxyAPI

Get one sephirah - sefirot meaning API with the paths that touch it

get_kabbalah_sephirot_id

Read-only

Return one sephirah in full: its Hebrew and English names, its pillar, its world, the sphere it carries under the requested system, what the emanation is said to hold, and every path that touches it with the letter and the tarot trump on each. Daat is addressable here as well, and its response says plainly that it is counted in some diagrams and not in others. Built for sephirot detail pages and for tree diagrams that load one node at a time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Sephirah identifier, one of keter, chokhmah, binah, chesed, gevurah, tiferet, netzach, hod, yesod, malkuth, daat. Matching folds case and punctuation.
`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.
`sephirotSystem`	No	Which reading assigns a sphere to each sephirah. The two were compared row by row and agree on all ten, so the answer is the same either way; the parameter exists so a caller knows which one produced it rather than assuming.	classical
`letterAttribution`	No	Which reading assigns the element, planet or sign to each letter. The seven double letters are the contested column and the four readings genuinely disagree on them; the twelve simple letters run in natural zodiacal order in all four. The golden-dawn member does NOT exchange He and Tzade, which is a later change from a different author.	sefer-yetzirah-gra

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`paths`	Yes
`world`	Yes
`hebrew`	Yes
`number`	Yes
`pillar`	Yes
`english`	Yes
`meaning`	Yes
`pillarName`	Yes
`attribution`	Yes
`conventions`	Yes
`romanization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "type": "string"
+    },
+    "conventions": {
+      "properties": {
+        "letterAttribution": {
+          "type": "string"
+        },
+        "sephirotSystem": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sephirotSystem",
+        "letterAttribution"
+      ],
+      "type": "object"
+    },
+    "english": {
+      "type": "string"
+    },
+    "hebrew": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "meaning": {
+      "type": "string"
+    },
+    "number": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "paths": {
+      "items": {
+        "properties": {
+          "attribution": {
+            "properties": {
+              "kind": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "value"
+            ],
+            "type": "object"
+          },
+          "from": {
+            "type": "string"
+          },
+          "letter": {
+            "type": "string"
+          },
+          "letterGlyph": {
+            "type": "string"
+          },
+          "path": {
+            "type": "number"
+          },
+          "to": {
+            "type": "string"
+          },
+          "trump": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "number": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "number",
+              "name"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "path",
+          "letter",
+          "letterGlyph",
+          "from",
+          "to",
+          "trump",
+          "attribution"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pillar": {
+      "type": "string"
+    },
+    "pillarName": {
+      "type": "string"
+    },
+    "romanization": {
+      "type": "string"
+    },
+    "world": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "number",
+    "hebrew",
+    "romanization",
+    "english",
+    "pillar",
+    "pillarName",
+    "world",
+    "attribution",
+    "meaning",
+    "paths",
+    "conventions"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/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 operation's safety profile is established. The description adds meaningful behavioral context by noting that Daat is addressable and that its response explicitly discloses how it is counted differently across diagrams. It also tells the agent exactly what content each returned sephirah record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each earning its place: the first front-loads the full return payload, the second adds the important Daat caveat, and the third names the target use cases. There is no filler or redundant repetition of schema field names.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a 100%-documented input schema, an output schema present, and annotations covering the read-only safety profile, the description supplies the remaining practical context: exact scope, Daat behavior, and intended page/tree use. Nothing essential for invoking this tool correctly is missing.

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%, and the input schema already documents each parameter thoroughly, including enums, defaults, case/punctuation folding, translation fallback, and compact shape behavior. The description only loosely references 'the requested system,' but it does not need to compensate because the schema carries the semantic weight.

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 opens with a specific verb, 'Return one sephirah in full,' and then enumerates the exact fields and associated data it returns, including names, pillar, world, sphere, emanations, and connected paths with letters and tarot trumps. This moves well beyond a restatement of the name or title and clearly distinguishes the tool from sibling tree or list-style endpoints.

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 states a clear context for use: 'Built for sephirot detail pages and for tree diagrams that load one node at a time.' This gives an agent a concrete sense of when to invoke this tool. It does not explicitly name alternatives or say when not to use it, but the single-node focus is unambiguous.

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?