Skip to main content
Glama

Numerology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Calculate Bridge Numbers - Numerology bridge numbers API

post_numerology_bridge
Read-only

Calculate four numerology Bridge numbers from a full birth name and birth date: Life Path and Expression, Expression and Soul Urge, Soul Urge and Personality, and Expression and Personality. Each bridge is the distance between two core numbers, from 0 to 8, where 0 means the two are already in harmony, and comes with guidance for closing the gap in the language set by lang. Built for personal development, coaching and personality analysis tools and AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesBirth day (1 to 31)
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
yearYesBirth year between 100 and 2100. Used to calculate the Life Path number via Pythagorean reduction.
monthYesBirth month (1 to 12)
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.
fullNameYesFull birth name as it appears on the birth certificate, first, middle and last names separated by spaces. Used to calculate the Expression, Soul Urge and Personality numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
expressionSoulUrgeYes
lifePathExpressionYes
soulUrgePersonalityYes
expressionPersonalityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / fullName / description
      Previous value: -"Full legal birth name as it appears on the birth certificate. Used to calculate Expression, Soul Urge, and Personality numbers. Include first, middle, and last names separated by spaces."New value: +"Full birth name as it appears on the birth certificate, first, middle and last names separated by spaces. Used to calculate the Expression, Soul Urge and Personality numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses."
    • addedOutput schema / properties / soulUrgePersonality
      Added value: +{
+  "properties": {
+    "bridge": {
+      "maximum": 8,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "from": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "name",
+        "number"
+      ],
+      "type": "object"
+    },
+    "meaning": {
+      "type": "string"
+    },
+    "to": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "name",
+        "number"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "bridge",
+    "from",
+    "to",
+    "meaning"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "lifePathExpression",
-  "expressionPersonality",
-  "expressionSoulUrge"
-]New value: +[
+  "lifePathExpression",
+  "expressionPersonality",
+  "soulUrgePersonality",
+  "expressionSoulUrge"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "expressionPersonality": {
+      "properties": {
+        "bridge": {
+          "maximum": 8,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "from": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "to": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "bridge",
+        "from",
+        "to",
+        "meaning"
+      ],
+      "type": "object"
+    },
+    "expressionSoulUrge": {
+      "properties": {
+        "bridge": {
+          "maximum": 8,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "from": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "to": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "bridge",
+        "from",
+        "to",
+        "meaning"
+      ],
+      "type": "object"
+    },
+    "lifePathExpression": {
+      "properties": {
+        "bridge": {
+          "maximum": 8,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "from": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "to": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "number"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "bridge",
+        "from",
+        "to",
+        "meaning"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "lifePathExpression",
+    "expressionPersonality",
+    "expressionSoulUrge"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  4. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": 15,
+    "fullName": "John William Smith",
+    "month": 7,
+    "year": 1990
+  }
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."
  5. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  6. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  7. 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, so the safety profile is covered. The description adds genuine behavioral context beyond that: the output range (0 to 8), the meaning of 0 (already in harmony), and that each bridge ships with gap-closing guidance in the selected language. It stops short of describing execution or failure behavior.

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 definition is front-loaded with the verb and the concrete bridge enumeration, which is the most useful information. The trailing sentence about target audiences ('personal development, coaching and personality analysis tools and AI agents') is soft filler that does not earn its place, costing it a point.

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 return shape needn't be explained, and annotations cover safety; the description fills the remaining gap by defining the bridge concept and its range. It is nearly complete, though a note on input constraints (e.g. name transliteration) delegated entirely to the schema would round it out.

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 six parameters thoroughly (including lang's BCP 47 enum and fullName's transliteration rules). The description only gestures at 'full birth name and birth date' and references lang, adding little beyond the structured data. Baseline 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 uses a specific verb ('Calculate') and resource ('numerology Bridge numbers') and enumerates the exact four bridges produced (Life Path/Expression, Expression/Soul Urge, Soul Urge/Personality, Expression/Personality). This clearly distinguishes it from sibling tools like post_numerology_life_path or post_numerology_expression, which compute the individual core numbers rather than the distances between them.

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 context ('Built for personal development, coaching and personality analysis tools') but never states when to choose this tool over the many sibling core-number tools, nor any exclusions or prerequisites. Usage is only implied, so it sits at the minimum-viable tier.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Numerology 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