Calculate a Destiny Matrix (numerology) reading from one or two dates of birth. Read-only, no auth.
Calculate relationship compatibility between two people from their dates of birth, using the Destiny Matrix numerology method. Returns a structured reading of the couple: shared core numbers plus text interpretations for relationship dynamics, finances, conflict points, children, and growth areas. Use this when a user asks how compatible two people are, or wants a numerology compatibility reading based on two birth dates.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language for the text interpretations: "en" (default), "ru", or "es". | |
| birthdate_a | Yes | First person's date of birth in DD-MM-YYYY format, e.g. "15-05-1990". | |
| birthdate_b | Yes | Second person's date of birth in DD-MM-YYYY format, e.g. "20-08-1995". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, and the description adds details about the return value: structured reading including shared core numbers and text interpretations for various aspects. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with purpose, and provides essential information without unnecessary details. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately explains what the tool returns. Parameters are fully covered in the schema. For a read-only tool with few dependencies, the description is complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all three parameters are already documented with descriptions. The description adds context about the date format (DD-MM-YYYY) and locale options, but does not significantly enhance understanding beyond the schema. Baseline is 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates relationship compatibility using the Destiny Matrix numerology method from two birth dates. The verb 'calculate' and resource 'compatibility' are specific, and it distinguishes from the sibling tool 'calculate_matrix' which likely handles single individuals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this when a user asks how compatible two people are, or wants a numerology compatibility reading based on two birth dates.' This provides clear context for when to use the tool. It does not explicitly state when not to use it, but the sibling tool name implies an alternative for single-person calculations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Calculate a Destiny Matrix (also known as "Matrix of Destiny" or numerology matrix) from a single date of birth. Returns a structured numerology reading: core numbers (1–22) for personality, talents, money, relationships, life purpose, and inherited/karmic patterns, each with a short text interpretation. Use this when a user asks to compute, build, or interpret a destiny matrix, or wants a numerology personality reading based on a birth date.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language for the text interpretations: "en" (default), "ru", or "es". | |
| birthdate | Yes | Date of birth in DD-MM-YYYY format (day-month-year), e.g. "15-05-1990". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and openWorldHint=false. Description adds value by detailing the output structure (core numbers, interpretations), which goes beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first states action and result, second gives usage context. Every sentence is essential and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two well-described parameters and no output schema, the description fully explains the return value structure, making it complete for an AI agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% description coverage for both parameters. The description does not add additional meaning beyond what the schema already provides, so baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates a Destiny Matrix from a birth date and returns a structured numerology reading. It distinguishes itself from the sibling tool 'calculate_compatibility' by focusing on a single person's reading.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description explicitly tells when to use: when asked to compute, build, or interpret a destiny matrix or numerology reading. It implies not for compatibility by having a separate sibling tool, but no explicit when-not statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Deterministic Pythagorean numerology MCP. Life Path, Destiny, Soul Urge, compatibility. No API key.
Calculate Human Design bodygraph charts, save people, compare charts, and analyse group dynamics.
Official Divine API MCP for Horoscope, Tarot, Numerology, and PDF Reports.
BaZi (八字) MCP gateway + 玄学社区. 12 tools (4 fortune + 5 forum + 3 meta). x-api-key required.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one computes a single person's matrix, the other computes compatibility between two people. There is no overlap or ambiguity.
Both tools follow a consistent 'calculate_' prefix and noun pattern (calculate_matrix, calculate_compatibility), making it predictable and easy to distinguish.
With only 2 tools, the server is minimal but well-scoped for the specific domain of Destiny Matrix numerology. It covers both individual and relationship readings, so the count feels appropriate if slightly low.
The tool set covers the two main functionalities for a Destiny Matrix server: individual matrix and compatibility. While advanced features like yearly forecasts or detailed house analysis are missing, the core use cases are addressed.
