Kabbalah MCP Server by RoxyAPI

Generate a birth profile - Hebrew birthday and birth angel API

post_kabbalah_birth_profile

Read-only

Return the Hebrew date of a birth, the next Hebrew birthday from targetDate or today, 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

Name	Required	Description	Default
`date`	Yes	Birth 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.
`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
`time`	No	Birth 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.
`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.
`timezone`	Yes	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.
`yearStart`	No	Which 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
`targetDate`	No	Date to count the next Hebrew birthday from, in YYYY-MM-DD format. Send the local date of the user for an exact answer: on the birthday itself the answer is that day. Defaults to today (UTC).
`afterSunset`	No	Set 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.
`angelDating`	No	How 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
`leapDayPolicy`	No	Where 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

Name	Required	Description	Default
`angels`	Yes
`sephirah`	Yes
`birthData`	Yes
`hebrewDate`	Yes
`conventions`	Yes
`hebrewBirthday`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / targetDate

Added value: +{
+  "description": "Date to count the next Hebrew birthday from, in YYYY-MM-DD format. Send the local date of the user for an exact answer: on the birthday itself the answer is that day. Defaults to today (UTC).",
+  "example": "2026-10-28",
+  "format": "date",
+  "type": "string"
+}

Changed1 schema field changedSep 20, 2026

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"
+}

Changed1 schema field changedSep 16, 2026

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."

First observedSep 6, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true and destructiveHint=false; the description goes well beyond them. It discloses that the Hebrew date is computed from a published calendar algorithm rather than looked up, that the sunset boundary is a caller assertion because no location is taken, and that the two rival angel-dating conventions are echoed in the response — all facts an agent cannot infer from annotations or schema. The compact-mode note (lossless, 40–52% fewer tokens) and the untyped-timezone/400 behaviour add further operational context.

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?

Two sentences, front-loaded with the returned values before the implementation caveats, which is the right order for a 10-parameter tool. Every clause carries information, though the closing 'Built for Jewish culture and education apps…' sentence is marketing-adjacent and only weakly helps selection. Length is proportionate to the tool's complexity.

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 and 100% schema description coverage, the description needn't explain return shapes, and it correctly spends its budget on computational provenance and the approximate-time caveat instead. It is essentially complete for correct invocation. The one real gap is sibling disambiguation against post_kabbalah_name_profile, which matters for a tool family this large.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the per-parameter descriptions are unusually thorough, so the baseline is 3. The description still adds cross-parameter meaning the schema does not: it explains why afterSunset is a typed field ('it depends on where you were'), why the time default to noon is dangerous ('the name read from the hour changes every twenty minutes'), and that the response echoes the angelDating convention, tying the enum to observable output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb-and-resource: it returns the Hebrew birth date, the next Hebrew birthday, three birth-tradition angel names, and the sephirah of the birth day, all derived from one birth moment. That is far more specific than the sibling names (get_kabbalah_names, get_kabbalah_letters) suggest. It stops short of 5 because it never contrasts itself with the closest sibling, post_kabbalah_name_profile, which an agent could easily confuse with a birth profile.

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?

Usage is implied through the closing sentence about Jewish culture/education apps, birth angel features, and products that want the Hebrew birthday keyed alongside other readings — this is audience framing rather than a when-to-use rule. There is no explicit exclusion or routing statement pointing at post_kabbalah_name_profile or get_kabbalah_daily. Some embedded guidance exists (e.g. 'Send the local date of the user for an exact answer'), but it lives in parameter text rather than the description.

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?