compatibility
Numerology compatibility between two Life Path numbers (1–9 or master 11/22/33).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | ||
| b | Yes |
Numerology MCP (Pythagorean)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only states basic purpose; does not explain output format, side effects, or behavior for invalid inputs. Agent lacks information on what the tool returns or how it operates.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, well-formed sentence that immediately conveys the tool's purpose. No wasted words; front-loaded with key information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the tool's apparent simplicity, the description lacks completeness. Without output schema or behavioral details, the agent cannot predict the tool's response or handle edge cases. More context could be added to compensate for absent annotations.
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 has 0% description coverage. The description adds that parameters are Life Path numbers in range 1-9 or 11/22/33, which provides some context beyond bare schema. However, it does not specify ordering, allowed outer values, or format constraints.
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?
Description clearly states it computes numerology compatibility between two Life Path numbers, and specifies the valid range. However, it does not differentiate from sibling tools like life_path or name_numbers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Sibling tools exist (life_path, name_numbers, numerology_profile) but the description gives no contextual cues.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool targets a distinct aspect of Pythagorean numerology (life path, name numbers, compatibility, full profile) with no overlap in purpose.
Naming Consistency5/5
All tool names follow a consistent pattern of lowercase, underscore-separated descriptive words (e.g., life_path, numerology_profile).
Tool Count5/5
With 4 tools, the server covers the core numerology functions without being too sparse or bloated, fitting its focused purpose.
Completeness5/5
The tool set covers all major Pythagorean numerology components: Life Path, Expression, Soul Urge, Personality, Birthday, Maturity, Personal Year, and compatibility.