Kabbalah MCP Server by RoxyAPI

Get one Hebrew letter - Hebrew letter meaning API

get_kabbalah_letters_id

Read-only

Return one Hebrew letter in full: its glyph and final form, its value under the standard and the finals reading, its Sefer Yetzirah class and what that class means, the element or planet or sign it carries under the requested reading, the tarot trump on its path, and the path number. Built for letter detail pages and for any reader who wants one row rather than all 22 letters.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Letter identifier, one of alef, bet, gimel, dalet, he, vav, zayin, chet, tet, yod, kaf, lamed, mem, nun, samekh, ayin, pe, tzadi, qof, resh, shin, tav. 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.
`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
`name`	Yes
`path`	Yes
`final`	Yes
`trump`	Yes
`value`	Yes
`letter`	Yes
`meaning`	Yes
`ordinal`	Yes
`finalValue`	Yes
`attribution`	Yes
`letterClass`	Yes
`classReading`	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": {
+      "properties": {
+        "kind": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "value"
+      ],
+      "type": "object"
+    },
+    "classReading": {
+      "type": "string"
+    },
+    "final": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "finalValue": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "letter": {
+      "type": "string"
+    },
+    "letterClass": {
+      "type": "string"
+    },
+    "meaning": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "ordinal": {
+      "type": "number"
+    },
+    "path": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "romanization": {
+      "type": "string"
+    },
+    "trump": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "number": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "name"
+      ],
+      "type": "object"
+    },
+    "value": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "letter",
+    "final",
+    "romanization",
+    "name",
+    "meaning",
+    "ordinal",
+    "value",
+    "finalValue",
+    "letterClass",
+    "classReading",
+    "attribution",
+    "trump",
+    "path"
+  ],
+  "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?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by detailing the response contents (glyph, final form, values, Sefer Yetzirah class, element/planet/sign, tarot trump, path number), giving the agent a concrete expectation of what will be returned without repeating the annotation info.

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 dense sentence that front-loads the core action ('Return one Hebrew letter in full') and then lists the returned fields and the intended use case. There is no filler, and it covers both purpose and usage in a compact form.

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 present, the description does not need to explain return values, and it does not attempt to. It covers the tool's purpose, content, and use case adequately. It does not mention error handling or edge cases, but the schema's enum and parameter descriptions cover validation. For a read-only, single-item retrieval tool, this is complete.

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%, meaning each parameter is already documented in the schema (id enum, lang options, compact flag, letterAttribution readings). The description does not add extra meaning beyond what the schema provides—it references 'requested reading' but the schema already explains the four readings in detail. Therefore the baseline of 3 applies.

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 clear verb ('Return') and a specific resource ('one Hebrew letter in full'), and enumerates the exact attributes returned. It explicitly differentiates from the sibling get_kabbalah_letters by noting 'one row rather than all 22 letters', making the tool's scope unmistakable.

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 a clear usage context: 'Built for letter detail pages and for any reader who wants one row rather than all 22 letters.' This implicitly contrasts with the plural sibling tool, indicating when to use this one. It does not enumerate all alternative tools, but for the primary distinction it is sufficient.

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?