Skip to main content
Glama
Sign In

Numerology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Calculate dual numerology - Pythagorean and Chaldean name number API

post_numerology_dual
Read-only

Calculate a name number in both Pythagorean and Chaldean numerology in one call and compare them. The Pythagorean side returns the Expression or Destiny number with master numbers 11, 22 and 33 kept; the Chaldean side returns the compound number from 10 to 52, the root, its planetary ruler and the compound interpretation; each shows its calculation name by name. An agreement flag and a plain-language note show whether the two systems point to the same single-digit energy, in the language set by lang. Built for system comparison tools, name analysis features and AI agents.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "David"
    },
    "name": "post_numerology_dual"
  }
}

Input 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
nameYesThe name to analyze in both systems. 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.
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

NameRequiredDescriptionDefault
nameYes
noteYes
chaldeanYes
agreementYes
pythagoreanYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The name to analyze in both systems."New value: +"The name to analyze in both systems. 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."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "agreement": {
+      "type": "boolean"
+    },
+    "chaldean": {
+      "properties": {
+        "calculation": {
+          "type": "string"
+        },
+        "caution": {
+          "type": "boolean"
+        },
+        "compound": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "compoundMeaning": {
+          "properties": {
+            "meaning": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "nature": {
+              "enum": [
+                "fortunate",
+                "unfortunate",
+                "mixed"
+              ],
+              "type": "string"
+            },
+            "number": {
+              "type": "number"
+            },
+            "sameAs": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "number",
+            "name",
+            "nature",
+            "meaning"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "planet": {
+          "type": "string"
+        },
+        "root": {
+          "type": "number"
+        },
+        "title": {
+          "type": "string"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "compound",
+        "root",
+        "total",
+        "calculation",
+        "planet",
+        "title",
+        "caution",
+        "compoundMeaning"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pythagorean": {
+      "properties": {
+        "calculation": {
+          "type": "string"
+        },
+        "keywords": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "number": {
+          "type": "number"
+        },
+        "title": {
+          "type": "string"
+        },
+        "type": {
+          "enum": [
+            "single",
+            "master"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "type",
+        "calculation",
+        "title",
+        "keywords"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "name",
+    "pythagorean",
+    "chaldean",
+    "agreement",
+    "note"
+  ],
+  "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: +[
+  {
+    "name": "David"
+  }
+]
    • 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.6/5.0
Behavior3/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 real behavioral detail (master numbers 11/22/33 preserved, Chaldean compound range 10-52, agreement-flag semantics), but much of it restates return content that the output schema already provides, and it says nothing about rate limits, cost, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body is one long run-on sentence packing system-by-system return details, flag semantics and audience notes. It is informative yet dense, with lower-value tail content ('Built for system comparison tools... AI agents') that does not earn its place.

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?

The description covers what is computed in each system and how the two are reconciled, and an output schema exists to carry return structure details. The only meaningful gap is routing guidance against the 20 sibling numerology tools, which is not addressed.

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 name, lang and compact thoroughly. The description only echoes the lang behavior ('in the language set by lang') without adding syntax, constraints, or edge cases beyond what the schema states, which is the expected baseline for full 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?

States a specific verb ('Calculate a name number') plus a specific resource and scope ('in both Pythagorean and Chaldean numerology in one call and compare them'). This clearly distinguishes it from single-system siblings such as post_numerology_chaldean and post_numerology_expression without requiring the schema to be opened.

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 by the dual-system framing ('compare them') and a target-audience line about system comparison tools, but there is no explicit when-to-use/when-not rule and no named alternative (e.g. use post_numerology_chaldean for Chaldean alone). An agent can infer the case, but must infer it.

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