MysticAPI

numerology

Numerology profile from a birth date (UTC): Pythagorean life path (master numbers 11/22/33 preserved), birthday number, personal year/month/day cycles, and tarot birth card. Time fields are accepted but only the date matters. Costs 1 call.

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>",
      "hour": "<hour>",
      "minute": "<minute>"
    },
    "name": "numerology"
  }
}

Input Schema

Name	Required	Description
`day`	Yes
`hour`	Yes	Hour 0-23 in UTC
`year`	Yes	4-digit year (UTC)
`month`	Yes
`minute`	Yes
`second`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 19, 2026
- changedInput schema / properties / hour / description
```
Previous value: -"Hour 0–23 in UTC"New value: +"Hour 0-23 in UTC"
```
AddedJul 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that time fields are ignored, that master numbers are preserved in the life path calculation, and that it costs 1 call. No contradictions.

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?

The description is a single sentence that efficiently lists the outputs and key behavioral notes. No filler, front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description covers the main outputs, parameter relevance, and cost. It lacks error handling or specifics on tarot birth card format, but is adequate for a simple tool.

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 coverage is only 33% (year and hour described). The description adds that hour/minute/second are accepted but ignored, which clarifies their meaning. Day and month have no description in schema or description, leaving some gaps. The description partially compensates for low coverage.

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 states it provides a numerology profile from a birth date, listing specific components (Pythagorean life path, birthday number, personal cycles, tarot birth card). This clearly distinguishes it from sibling tools like 'bodygraph' or 'ephemeris' which are different divinatory systems.

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?

The description explicitly notes that time fields are accepted but only the date matters, guiding the agent on irrelevant parameters. It also mentions cost. However, it does not provide explicit when-to-use vs alternatives, but context with siblings makes it clear.

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

All MysticAPI 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?