Skip to main content
Glama

Kabbalah MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Generate a birth profile - Hebrew birthday and birth angel API

post_kabbalah_birth_profile
Read-only

Return the Hebrew date of a birth, the Hebrew birthday that follows it, the three birth names of the Renaissance angel tradition and the sephirah of the birth day, from one birth moment. The Hebrew date is computed from the published calendar algorithm rather than looked up, the sunset boundary is a typed request field because it depends on where you were, and the two rival ways of dating the first name are a typed convention the response echoes. Built for Jewish culture and education apps, birth angel features and any product that wants the Hebrew birthday on the same key as the rest of its readings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD, proleptic Gregorian. Dates before the 1582 reform are read on the same proleptic reckoning rather than switched to the Julian calendar.
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
timeNoBirth time in HH:MM:SS local to the timezone field. Defaults to noon when omitted, which is stated because the name read from the hour changes every twenty minutes and a defaulted time cannot be precise.
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.
timezoneYesIANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.
yearStartNoWhich date the civil wheel of five day periods opens on. Both are conventions rather than facts: the equinox itself moves inside a window that covers both days, and it fell on 20 March in 2026. march-21 is the pinned published wheel and march-20 is that wheel shifted one day. Ignored when angelDating is solar-longitude.march-21
afterSunsetNoSet true when the moment falls after nightfall, which advances the Hebrew date by one day because the Hebrew day begins in the evening. It is a caller assertion rather than a computation, since sunset depends on a place and this conversion takes none.
angelDatingNoHow the name of the day is found. Use solar-longitude for the exact five degree arc the Sun stood in at the birth moment, or lenain-blocks for the fixed civil calendar of five day periods. The Sun does not move at a constant rate, so the two drift apart by up to about three days by early August and were never reconciled.solar-longitude
leapDayPolicyNoWhere 29 February falls. The civil wheel was built for a 365 day year and has no slot for it, so published tables differ: extend-previous reads the day as part of the period ending 28 February, next-angel reads it as the opening of the period starting 1 March. Ignored when angelDating is solar-longitude.extend-previous

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
angelsYes
sephirahYes
birthDataYes
hebrewDateYes
conventionsYes
hebrewBirthdayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "angels": {
+      "items": {
+        "properties": {
+          "choir": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "reading": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "romanization": {
+            "type": "string"
+          },
+          "traditionalName": {
+            "type": "string"
+          },
+          "window": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "role",
+          "number",
+          "name",
+          "romanization",
+          "traditionalName",
+          "choir",
+          "window",
+          "reading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "birthData": {
+      "properties": {
+        "date": {
+          "type": "string"
+        },
+        "time": {
+          "type": "string"
+        },
+        "timezone": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "date",
+        "time",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    "conventions": {
+      "properties": {
+        "afterSunset": {
+          "type": "boolean"
+        },
+        "angelDating": {
+          "type": "string"
+        },
+        "leapDayPolicy": {
+          "type": "string"
+        },
+        "yearStart": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "angelDating",
+        "yearStart",
+        "leapDayPolicy",
+        "afterSunset"
+      ],
+      "type": "object"
+    },
+    "hebrewBirthday": {
+      "properties": {
+        "date": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hebrewYear": {
+          "type": "number"
+        },
+        "note": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "date",
+        "hebrewYear"
+      ],
+      "type": "object"
+    },
+    "hebrewDate": {
+      "properties": {
+        "afterSunset": {
+          "type": "boolean"
+        },
+        "day": {
+          "type": "number"
+        },
+        "hebrew": {
+          "type": "string"
+        },
+        "leapYear": {
+          "type": "boolean"
+        },
+        "month": {
+          "type": "string"
+        },
+        "monthNumber": {
+          "type": "number"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "year",
+        "month",
+        "monthNumber",
+        "day",
+        "leapYear",
+        "hebrew",
+        "afterSunset"
+      ],
+      "type": "object"
+    },
+    "sephirah": {
+      "properties": {
+        "english": {
+          "type": "string"
+        },
+        "hebrew": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "number": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "romanization": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "english",
+        "hebrew",
+        "romanization",
+        "meaning"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "birthData",
+    "hebrewDate",
+    "hebrewBirthday",
+    "angels",
+    "sephirah",
+    "conventions"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavioral context: the Hebrew date is computed via a published algorithm rather than looked up, the sunset field is a caller assertion because it depends on location, and the two naming conventions are typed and echoed. This goes beyond the annotations and helps the agent understand why certain fields exist and how the computation works.

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 two sentences with no wasted words. The first sentence front-loads the main function, and the second packs in the key design rationales (computation, sunset dependency, naming conventions) without redundancy. It is dense but efficient.

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 (9 parameters, 4 enums, output schema present), the description covers the essential behavioral and domain context, such as the computation method and the two conventions. It does not explain every parameter (schema does that) nor describe return format (output schema exists), so it is reasonably complete for an agent to use 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 the schema already documents all parameters. The description does not add detailed parameter-level semantics beyond what the schema provides, though it does offer a high-level explanation of the sunset and angelDating concepts. This aligns with the baseline of 3 for high coverage.

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') with a clear resource ('birth profile') and enumerates the exact outputs: Hebrew date, following Hebrew birthday, three birth names, and sephirah. It distinguishes from siblings by focusing on birth-specific data, while other tools like get_kabbalah_names or get_kabbalah_ciphers are clearly different in scope.

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 gives a target audience ('Built for Jewish culture and education apps, birth angel features...') which implies when to use it, but it does not explicitly state when to use this instead of sibling tools like post_kabbalah_name_profile or get_kabbalah_daily. There is no mention of alternatives or exclusions, so guidance is only implied.

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