ArcFlow Destiny Matrix
Server Details
Calculate a Destiny Matrix (numerology) reading from one or two dates of birth. Read-only, no auth.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one computes a single person's destiny matrix, the other calculates compatibility between two people. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: 'calculate_matrix' and 'calculate_compatibility', which makes them predictable and easy to distinguish.
With only 2 tools, the set is quite minimal. While it covers the core operations for a niche numerology server, it feels slightly thin for broader use cases.
The tools cover the primary requests (individual matrix and compatibility), but missing features like detailed number explanations or report generation leave notable gaps.
Available Tools
2 toolscalculate_compatibilityCalculate Destiny Matrix CompatibilityARead-onlyInspect
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". |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds that it returns a structured reading with specific content (numbers, interpretations), but does not disclose any additional behavioral traits beyond what annotations provide.
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 two sentences with no wasted words. First sentence states purpose and method, second provides usage guidance. Front-loaded and efficient.
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 the tool has 3 parameters and no output schema, the description adequately covers what the tool does and returns (shared core numbers, text interpretations for multiple aspects). It also provides usage guidance, making it complete for selection and invocation.
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 description coverage is 100%, so the schema already documents all parameters. The description adds minimal context beyond the schema, only mentioning 'dates of birth' and language options. Baseline 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 relationship compatibility using Destiny Matrix numerology from two birth dates, and distinguishes it from the sibling tool 'calculate_matrix' which likely computes individual matrices.
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', providing clear usage context. It does not explicitly state when not to use or mention alternatives, but the sibling tool name gives indirect differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
calculate_matrixCalculate Destiny MatrixARead-onlyInspect
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". |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so no contradiction. The description adds value by detailing the output categories and interpretations, providing behavioral context 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 concise sentences: first states purpose and output, second gives usage guidance. 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.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, high schema coverage, and readOnly hint, the description provides a thorough overview of inputs, outputs, and appropriate use cases, leaving no major gaps.
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 description coverage is 100%, so baseline is 3. The description does not add new information about parameters beyond reinforcing that locale controls language; it is adequate but not exceptional.
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 it calculates a Destiny Matrix from a single date of birth and lists specific outputs (personality, talents, etc.). It implicitly distinguishes from the sibling 'calculate_compatibility' by emphasizing 'single date of birth'.
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 states when to use this tool: when users ask to compute, build, or interpret a destiny matrix or want a numerology reading. It does not mention when not to use it or explicitly reference the sibling tool, but the guidance is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!