Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Soul Urge / Heart's Desire (kabbalistic-strict)

astroway_numerology_kabbalistic_strict_soul_urge
Read-onlyIdempotent

Calculate the Soul Urge number from the vowels in a full birth name using the Kabbalistic (Mathers strict) numerology system. Provide name and birth date to get the result.

Instructions

Calculate the Soul Urge number from the vowels of the full birth name. Numerology: Kabbalistic (Mathers strict) system.

[Group: Numerology: Kabbalistic (Mathers strict)] [Endpoint: POST /v1/numerology/kabbalistic-strict/soul-urge] [Required: name, date] [Cost: 10 credits (Tier 1)]

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": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "astroway_numerology_kabbalistic_strict_soul_urge"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nameYes

Output Schema

NameRequiredDescriptionDefault
dateNo
nameNo
systemNo
soulUrgeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds genuinely new behavioral context the schema does not carry: the cost of 10 credits (Tier 1) and the POST endpoint, which matter for a paid computation. It does not describe what the result contains, but an output schema exists.

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?

Two tight sentences front-load the action and method, followed by short bracketed metadata lines. The [Required: name, date] line duplicates the schema's required array, but the cost and group lines earn their space.

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?

With an output schema present, return values needn't be explained, and annotations cover the safety profile. What remains under-specified is minor: why a birth date is required for a name-vowel calculation and how this strict variant differs from its non-strict twin.

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 description coverage is 0%, so the description must carry the load. It does clarify that `name` means the full birth name (which drives the vowel extraction), but `date` is never mentioned even though it is required — the agent gets the date format from the regex pattern only, not from any statement of why a date is needed for a name-based calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Calculate the Soul Urge number") and adds the algorithmic basis ("from the vowels of the full birth name") plus the system ("Kabbalistic (Mathers strict)"). That system label does differentiate it from the Pythagorean/Vedic/Chaldean/non-strict soul-urge siblings, though the description never names a sibling to route away from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion, and no mention of the alternative soul-urge tools (e.g. astroway_numerology_kabbalistic_soul_urge or the Pythagorean variants). The system tag only implies context; the agent must infer selection criteria itself.

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

Deploy Server

Other Tools