Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Soul Urge / Heart's Desire (kabbalistic)

astroway_numerology_kabbalistic_soul_urge
Read-onlyIdempotent

Calculate the Kabbalistic Soul Urge number from vowels in a full birth name to reveal core motivations. Provide name and birth date for phonetic numerology analysis.

Instructions

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

[Group: Numerology: Kabbalistic (phonetic)] [Endpoint: POST /v1/numerology/kabbalistic/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_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.4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavioral information: the endpoint (POST /v1/numerology/kabbalistic/soul-urge) and a cost of 10 credits (Tier 1), which matters for spend decisions. It does not describe the return payload, but an output schema exists to cover that.

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 purpose sentence is front-loaded and terse, followed by compact bracketed metadata lines. Every line carries usable information (group, endpoint, required params, cost), though the [Group: ...] line largely duplicates the tool name.

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

Completeness3/5

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

Annotations and an output schema relieve the description of safety and return-value duties, and cost/endpoint details are present. Still missing are the distinction from the strict-Kabbalistic sibling and any explanation of the date parameter's role in a vowel-based calculation, both of which an agent would want before invoking it.

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 schema alone gives only types and a date regex. The description compensates partially by clarifying that 'name' means the full birth name (not a nickname), which is meaningful, and restates the required set. It adds nothing about why a date is required for a name-derived vowel calculation, which is a genuine point of confusion.

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 (Calculate) plus the exact resource (Soul Urge number) and even the derivation method (vowels of the full birth name) within the Kabbalistic phonetic system. It is clear on its own, but there is a sibling astroway_numerology_kabbalistic_strict_soul_urge that it never differentiates itself from, leaving a real ambiguity among near-identical names.

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 mention of when to prefer the strict Kabbalistic variant, Vedic, Pythagorean, or Chaldean soul-urge siblings, and no prerequisites beyond listing required params. An agent must infer the selection rule purely from naming conventions.

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