Numerology MCP Server by RoxyAPI

Calculate numerology compatibility - Love match scoring API

post_numerology_compatibility

Read-only

Calculate numerology compatibility between two people from their Life Path, Expression and Soul Urge numbers. Send each person as a full birth name with a birth date, or as precomputed numbers, and mix the two modes freely across the pair. The response returns an overall score from 50 to 100 with its rating, a score and description for each number pair, and the strengths, challenges and advice for the relationship, in the language set by lang. Built for dating apps, matchmaking, relationship coaching and AI companions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "person1": "<person1>",
      "person2": "<person2>"
    },
    "name": "post_numerology_compatibility"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`person1`	Yes
`person2`	Yes

Output Schema

Name	Required	Description	Default
`advice`	Yes
`rating`	Yes
`lifePath`	Yes
`soulUrge`	Yes
`strengths`	Yes
`challenges`	Yes
`expression`	Yes
`overallScore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / person1 / x-required-any-of

Added value: +[
+  [
+    "fullName",
+    "year",
+    "month",
+    "day"
+  ],
+  [
+    "lifePath",
+    "expression",
+    "soulUrge"
+  ]
+]

addedInput schema / properties / person2 / x-required-any-of

Added value: +[
+  [
+    "fullName",
+    "year",
+    "month",
+    "day"
+  ],
+  [
+    "lifePath",
+    "expression",
+    "soulUrge"
+  ]
+]

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "advice": {
+      "type": "string"
+    },
+    "challenges": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "expression": {
+      "properties": {
+        "compatibility": {
+          "type": "number"
+        },
+        "description": {
+          "type": "string"
+        },
+        "person1": {
+          "type": "number"
+        },
+        "person2": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "person1",
+        "person2",
+        "compatibility",
+        "description"
+      ],
+      "type": "object"
+    },
+    "lifePath": {
+      "properties": {
+        "compatibility": {
+          "type": "number"
+        },
+        "description": {
+          "type": "string"
+        },
+        "person1": {
+          "type": "number"
+        },
+        "person2": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "person1",
+        "person2",
+        "compatibility",
+        "description"
+      ],
+      "type": "object"
+    },
+    "overallScore": {
+      "type": "number"
+    },
+    "rating": {
+      "type": "string"
+    },
+    "soulUrge": {
+      "properties": {
+        "compatibility": {
+          "type": "number"
+        },
+        "description": {
+          "type": "string"
+        },
+        "person1": {
+          "type": "number"
+        },
+        "person2": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "person1",
+        "person2",
+        "compatibility",
+        "description"
+      ],
+      "type": "object"
+    },
+    "strengths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "overallScore",
+    "rating",
+    "lifePath",
+    "expression",
+    "soulUrge",
+    "strengths",
+    "challenges",
+    "advice"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

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

Changed1 schema field changedAug 17, 2026

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

Changed1 schema field changedJul 22, 2026

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

Changed1 schema field changedJul 22, 2026

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

First observedJul 8, 2026

TDQS

A3.8/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 safety is covered. The description adds genuine behavioral detail beyond that: the overall score range is 50–100 with a rating, per-number-pair scores and descriptions, plus strengths, challenges and advice, all localized by lang. What remains unstated is whether the score is deterministic or how invalid inputs are handled.

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?

Three sentences, front-loaded with the core operation, then input modes, then return shape. Dense and mostly waste-free; the closing 'Built for dating apps, matchmaking...' sentence is marketing framing rather than decision-relevant information.

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 needn't detail return values, and one annotation pair covers the safety profile. Given the nested two-person schema and ten-language localization, the description supplies the missing mode-mixing rule and localization behavior, leaving only edge cases like input validation unaddressed.

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 50%, so the description must compensate, and it does on the key point the schema cannot express: the two input modes may be mixed freely across person1 and person2, which the nested x-required-any-of constraints read as per-person only. It also ties lang to the language of the returned narrative, adding meaning beyond the enum list. It says nothing about the compact flag.

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?

States a specific verb and resource — calculating numerology compatibility between two people — and names the exact inputs (Life Path, Expression, Soul Urge). It is clearly distinguishable from single-aspect siblings like post_numerology_life_path or post_numerology_soul_urge, though it never names a sibling to contrast with explicitly.

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 does give concrete invocation guidance: each person can be sent as a full birth name plus birth date, or as precomputed numbers, and the two modes can be mixed across the pair. However, it offers no when-not conditions, no prerequisites, and no explicit routing away from the many sibling numerology tools.

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 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?