Skip to main content
Glama

Kabbalah MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Get the Tree of Life - sephirot and 22 paths API with typed school variants

get_kabbalah_tree
Read-only

Return the whole Tree of Life in one call: the ten sephirot with their Hebrew, their pillar, their world and their sphere, Daat beside them, the 22 paths with the letter and the tarot trump on each, the four worlds under both mappings that are in circulation, and the lightning flash order. The school splits are typed request parameters rather than hidden defaults, and the response echoes which arrangement and which reading produced it. Built for Tree of Life diagrams, tarot path features and reference pages that need the structure rather than a picture of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
compactNoSet 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.
treeVariantNoWhich arrangement of the twenty two paths. The 1652 arrangement, in which Malkuth carries three paths, is the only one with a published table that letters every path, so it is the only member.kircher
sephirotSystemNoWhich 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
letterAttributionNoWhich 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
NameRequiredDescriptionDefault
pathsYes
worldsYes
sephirotYes
conventionsYes
lightningFlashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conventions": {
+      "properties": {
+        "letterAttribution": {
+          "type": "string"
+        },
+        "sephirotSystem": {
+          "type": "string"
+        },
+        "treeVariant": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "treeVariant",
+        "sephirotSystem",
+        "letterAttribution"
+      ],
+      "type": "object"
+    },
+    "lightningFlash": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "sephirot": {
+      "items": {
+        "properties": {
+          "attribution": {
+            "type": "string"
+          },
+          "english": {
+            "type": "string"
+          },
+          "hebrew": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "number": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "pillar": {
+            "type": "string"
+          },
+          "pillarName": {
+            "type": "string"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "world": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "number",
+          "hebrew",
+          "romanization",
+          "english",
+          "pillar",
+          "pillarName",
+          "world",
+          "attribution",
+          "meaning"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "worlds": {
+      "items": {
+        "properties": {
+          "english": {
+            "type": "string"
+          },
+          "hebrew": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "sephirot": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "sephirotAlternate": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "hebrew",
+          "romanization",
+          "english",
+          "sephirot",
+          "sephirotAlternate"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sephirot",
+    "paths",
+    "worlds",
+    "lightningFlash",
+    "conventions"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/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, covering the safety profile. The description adds valuable context beyond that: it discloses the response echoes which arrangement and reading produced it, notes that school splits are typed parameters rather than hidden defaults, and specifies that translation coverage varies with English fallback (though that detail is in the schema). It accurately reflects the read-only nature without contradiction, and the extra context about response echoing is not available from 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 a single paragraph but is well-organized and front-loads the core purpose. Each clause adds information: the content list, the design decision, and the intended use cases. It avoids redundancy and keeps sentences focused, though it is slightly longer than strictly necessary. The structure is clear and efficient, earning a 4.

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 tool's complexity (5 parameters, 4 enums) and the presence of an output schema, the description covers the key aspects: what data is returned, the design choice around parameters, and the echo of the arrangement. It does not mention error handling or edge cases, but those are likely covered by the output schema. The description is sufficient for an agent to understand the tool's purpose and expected output without missing critical context.

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 schema covers 100% of parameters with detailed descriptions, including enums and defaults. The tool description adds only a high-level note that school splits are typed request parameters, which is already evident from the schema. It does not elaborate on parameter semantics beyond what the schema provides, so it meets the baseline of 3 but does not exceed it.

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 precise verb and resource ('Return the whole Tree of Life in one call') and enumerates the exact components delivered (ten sephirot with Hebrew, pillar, world, sphere; Daat; 22 paths with letter and tarot trump; four worlds; lightning flash order). It also distinguishes itself from siblings by stating it is 'Built for Tree of Life diagrams, tarot path features and reference pages that need the structure rather than a picture of it,' clearly separating it from tools like get_kabbalah_letters or get_kabbalah_sephirot_id.

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?

The description implies usage for structural references and notes that school splits are exposed as parameters, but it does not explicitly state when to choose this tool over alternatives, nor does it name any sibling tool or provide exclusion criteria. The mention of 'structure rather than a picture' hints at a use case but leaves the agent to infer the boundary with other kabbalah tools. No explicit 'use when X' or 'not for Y' guidance is given.

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 toolsInspect
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