numerology-api

numerology_profile

Full deterministic Pythagorean numerology profile from a name and birth date: Life Path, Expression/Destiny, Soul Urge, Personality, Birthday, Maturity and Personal Year, each with reduction trail. No AI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>"
    },
    "name": "numerology_profile"
  }
}

Input Schema

Name	Required	Description	Default
`day`	Yes
`name`	No
`year`	Yes
`month`	Yes
`targetYear`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description specifies 'deterministic' and 'No AI,' but lacks details on side effects, authorization needs, or what happens if required parameters like name are missing (name is not required in schema but needed for some outputs). No annotations are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the purpose and lists key outputs efficiently. It avoids superfluous 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 listing output components, the description lacks details on return format, parameter constraints (e.g., required name for full profile), and context for targetYear. No output schema exists to compensate, leaving gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds no parameter-level details. It does not explain the meaning or constraints of each parameter, such as name format or targetYear's role in Personal Year calculation.

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 it provides a 'Full deterministic Pythagorean numerology profile' from name and birth date, listing specific outputs like Life Path, Expression/Destiny, and Personal Year. It distinguishes from siblings by implying a comprehensive profile vs single-number 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for full profile computation but does not explicitly state when to use this tool over siblings like compatibility, life_path, or name_numbers. No guidance on prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All numerology-api tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?