Skip to main content
Glama

ArcFlow Destiny Matrix

by io.github.mlch

Calculate Destiny Matrix

calculate_matrix
Read-only

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoLanguage for the text interpretations: "en" (default), "ru", or "es".
birthdateYesDate of birth in DD-MM-YYYY format (day-month-year), e.g. "15-05-1990".

TDQS

A4.3/5.0
Behavior4/5

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.

Conciseness5/5

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.

Completeness5/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

All ArcFlow Destiny Matrix 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

A4.4/5.0
Disambiguation5/5

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.

Naming Consistency5/5

Both tools follow a consistent 'calculate_' prefix and noun pattern (calculate_matrix, calculate_compatibility), making it predictable and easy to distinguish.

Tool Count4/5

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.

Completeness4/5

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.

Resources