Skip to main content
Glama

Kabbalah MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

List gematria ciphers - gematria methods API with provenance on every row

get_kabbalah_ciphers
Read-only

Return the full catalogue of gematria methods this API computes: eleven rabbinic ciphers, two substitution transformations, and the three Latin alphabet ciphers, each with its definition, its provenance class, the century of its tradition and the sources it was taken from. Every entry states whether it is rabbinic or a Renaissance Christian or modern Latin cipher, so a product never presents one tradition as the other. Built for calculators that want to show a reader which method produced a number and where the method comes from.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
ciphersYes
latinCiphersYes
transformationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "ciphers": {
+      "items": {
+        "properties": {
+          "century": {
+            "type": "string"
+          },
+          "computed": {
+            "type": "boolean"
+          },
+          "definition": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "multiValued": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sources": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tradition": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "tradition",
+          "century",
+          "definition",
+          "computed",
+          "sources"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latinCiphers": {
+      "items": {
+        "properties": {
+          "century": {
+            "type": "string"
+          },
+          "computed": {
+            "type": "boolean"
+          },
+          "definition": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "multiValued": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sources": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tradition": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "tradition",
+          "century",
+          "definition",
+          "computed",
+          "sources"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "transformations": {
+      "items": {
+        "properties": {
+          "century": {
+            "type": "string"
+          },
+          "computed": {
+            "type": "boolean"
+          },
+          "definition": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "multiValued": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sources": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tradition": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "tradition",
+          "century",
+          "definition",
+          "computed",
+          "sources"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "total",
+    "ciphers",
+    "transformations",
+    "latinCiphers"
+  ],
+  "type": "object"
+}
  2. First observed

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. The description adds useful behavioral context beyond that: every entry 'states whether it is rabbinic or a Renaissance Christian or modern Latin cipher, so a product never presents one tradition as the other,' plus provenance class, century, and sources are guaranteed per row.

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 front-loaded with the core scope in the first sentence, immediately followed by provenance guarantees and then the intended consumer. Every sentence earns its place, with no filler or repetition.

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?

There are no required parameters, the output schema describes return shape, and annotations cover the read-only safety profile. The description supplies the remaining context: what the catalogue contains, how each entry is classified, and why a product would use it. Nothing needed for correct invocation 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%, so both lang and compact are fully documented in the input schema with defaults and behavior. The description adds no parameter-specific meaning, which is acceptable given the schema carries the full burden.

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, 'Return', and a resource, 'the full catalogue of gematria methods', then enumerates the exact contents: eleven rabbinic ciphers, two substitution transformations, and three Latin alphabet ciphers. It clearly distinguishes this metadata/reference tool from computation-focused siblings like get_kabbalah_daily or post_kabbalah_gematria.

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 final sentence, 'Built for calculators that want to show a reader which method produced a number and where the method comes from,' gives a clear intended-use context. It does not explicitly name alternatives or when-not-to-use, but the catalogue framing and sibling names make the distinction evident.

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