Skip to main content
Glama

Numerology MCP Server by RoxyAPI

by com.roxyapi

Calculate Compatibility - Relationship dynamics between two people

post_numerology_compatibility
Read-only

Calculate numerology compatibility between two people using Pythagorean numerology. Accepts two input modes per person: pre-calculated Life Path, Expression, and Soul Urge numbers, or raw name and birthdate for automatic calculation. You can mix modes across persons (e.g. numbers for person1, raw inputs for person2). Provides comprehensive relationship analysis with overall compatibility score (0-100), individual aspect compatibility (Life Path 50% weight, Expression 30%, Soul Urge 20%), relationship strengths, challenges, and practical advice. Uses detailed compatibility matrix for all number combinations. Perfect for dating apps, relationship counseling platforms, matchmaking services, and compatibility tools. Get actionable insights for improving relationship dynamics.

Input Schema

TableJSON 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
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.
person1Yes
person2Yes

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark this as read-only and non-destructive, so no side-effect warnings are needed. The description importantly reveals what happens with input modes—numbers, raw name/birthdate, or a mix—and what the output will contain: a weighted 0-100 score, aspect scores, strengths, challenges, and advice.

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 core functional sentences are dense and useful, but the ending has promotional filler about dating apps and 'actionable insights' that does not help an agent select or invoke the tool. The key behavioral and output info is still early enough, but the description could be tightened.

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?

There is no output schema, but the description makes up for it by describing the composite score, individual aspect weights, and the strengths/challenges/advice outputs. It does not discuss validation or precedence behavior for partially filled input modes, but enough is present for reliable tool use.

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?

With 50% schema description coverage, the description adds real semantics beyond the schema by explaining the family of usable inputs per person and the fact that the two input modes can be mixed. It does not need to re-export lang or compact details because the schema already covers those cleanly.

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 clearly states a declarative and specific resource: 'Calculate numerology compatibility between two people using Pythagorean numerology.' It stands apart from sibling tools such as post_numerology_life_path or post_numerology_soul_urge because it is explicitly a two-person compatibility analysis, not a single-number reading.

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 contextual use cases like dating apps, relationship counseling, and matchmaking, and clearly describes the two supported input modes. However, it does not explicitly say when not to use this tool or direct the agent to a single-person sibling tool for one-person numerology questions.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool targets a specific numerology calculation or lookup, and descriptions make the intended resource clear. A few tools have possible overlap—such as post_numerology_daily vs. post_numerology_personal_day and post_numerology_business_name vs. post_numerology_chaldean—but the distinctions are recoverable from context.

Naming Consistency5/5

Tool names follow a consistent pattern: get_numerology_* for lookups and post_numerology_* for calculations, all using snake_case. This makes both the operation type and the resource target predictable across the whole server.

Tool Count3/5

20 tools is on the heavy side for a single numerology server, and some tools such as post_numerology_chart and get_numerology_meanings_number overlap with or aggregate the results of individual calculation endpoints. The count is not unreasonable for a broad numerology API, but it stretches into a large surface area for an agent to navigate.

Completeness5/5

The server covers the major numerology surface well: core core numbers, personal cycles, karmic calculations, compatibility, Chaldean/Pythagorean variants, business name analysis, and a comprehensive chart endpoint. Only very niche numerology features are absent, so the tool set can serve end-to-end yoga use cases without obvious dead ends.

Resources