Skip to main content
Glama

Soul Urge / Heart's Desire (kabbalistic)

astroway_numerology_kabbalistic_soul_urge
Read-onlyIdempotent

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
yRuleNoHow Y is read for soul urge and personality. `vowel` (default): Y is always a vowel. `sound`: the rule of Hans Decoz ("Numerology: Key to Your Inner Self"), Y read by sound: Y is a consonant when the letter right before or right after it in the same word is A, E, I, O or U, otherwise a vowel. Yolanda, Maya and Bryan take Y as a consonant, Lynn as a vowel. Life path, expression, maturity and balance do not depend on it. The value used is echoed in `conventions.yRule`.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
dateNo
nameNo
systemNo
soulUrgeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / yRule
      Added value: +{
      +  "description": "How Y is read for soul urge and personality. `vowel` (default): Y is always a vowel. `sound`: the rule of Hans Decoz (\"Numerology: Key to Your Inner Self\"), Y read by sound: Y is a consonant when the letter right before or right after it in the same word is A, E, I, O or U, otherwise a vowel. Yolanda, Maya and Bryan take Y as a consonant, Lynn as a vowel. Life path, expression, maturity and balance do not depend on it. The value used is echoed in `conventions.yRule`.",
      +  "enum": [
      +    "vowel",
      +    "sound"
      +  ],
      +  "type": "string"
      +}
  2. Changed7 schema fields changed
    • removedOutput schema / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / soulUrge / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "isMaster": {
      -        "anyOf": [
      -          {
      -            "type": "boolean"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "meaning": {
      -        "anyOf": [
      -          {
      -            "additionalProperties": {},
      -            "properties": {
      -              "archetype": {
      -                "anyOf": [
      -                  {
      -                    "type": "string"
      -                  },
      -                  {
      -                    "type": "null"
      -                  }
      -                ]
      -              },
      -              "number": {
      -                "anyOf": [
      -                  {
      -                    "type": "number"
      -                  },
      -                  {
      -                    "type": "null"
      -                  }
      -                ]
      -              },
      -              "shortRead": {
      -                "anyOf": [
      -                  {
      -                    "type": "string"
      -                  },
      -                  {
      -                    "type": "null"
      -                  }
      -                ]
      -              },
      -              "strengths": {
      -                "anyOf": [
      -                  {
      -                    "items": {
      -                      "anyOf": [
      -                        {
      -                          "type": "string"
      -                        },
      -                        {
      -                          "type": "null"
      -                        }
      -                      ]
      -                    },
      -                    "type": "array"
      -                  },
      -                  {
      -                    "type": "null"
      -                  }
      -                ]
      -              }
      -            },
      -            "type": "object"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "raw": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "reduced": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "steps": {
      -        "anyOf": [
      -          {
      -            "items": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": "array"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "isMaster": {
      +        "type": [
      +          "boolean",
      +          "null"
      +        ]
      +      },
      +      "meaning": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": {},
      +            "properties": {
      +              "archetype": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "number": {
      +                "type": [
      +                  "number",
      +                  "null"
      +                ]
      +              },
      +              "shortRead": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "strengths": {
      +                "anyOf": [
      +                  {
      +                    "items": {
      +                      "type": [
      +                        "string",
      +                        "null"
      +                      ]
      +                    },
      +                    "type": "array"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              }
      +            },
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "raw": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "reduced": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "steps": {
      +        "anyOf": [
      +          {
      +            "items": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / system / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / system / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: the endpoint, the required inputs, and a billing cost of 10 credits (Tier 1), which matters for an agent deciding whether to call it. It does not explain what the response contains, but an output schema exists, so that omission is acceptable.

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?

One front-loaded purpose sentence followed by a compact bracketed metadata block (group, endpoint, required inputs, cost) — no filler, and the cost/billing fact is visible at a glance. Slightly terse: the metadata block consumes roughly half the text without adding differentiation among sibling tools.

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?

For a deterministic single-number computation with an output schema, annotations covering the safety profile, and explicit cost and endpoint disclosure, most of what an agent needs in order to call it is present. The remaining gap is disambiguation from the sibling 'kabbalistic_strict_soul_urge' and any note on what the resulting number signifies, neither of which the description addresses.

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 60%, and the description echoes the two required parameters and clarifies that 'name' should be the full birth name (vowels are taken from it), which adds real meaning beyond the schema's minLength/maxLength constraints. However, it never mentions 'yRule', the one enum parameter that materially changes a vowel-based calculation, nor the compact-mode 'fields'/'precision' parameters, leaving the remaining coverage gap partly unfilled.

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') plus the computation basis ('from the vowels of the full birth name') and the system ('Kabbalistic (phonetic)'). It separates itself from Chaldean/Pythagorean/Vedic siblings by naming the system, but says nothing about how it differs from the near-identically named sibling 'kabbalistic_strict_soul_urge', which an agent cannot resolve from the description alone.

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 or when-not guidance, no statement of prerequisites beyond the metadata line 'Required: name, date', and no routing instruction among the many sibling soul-urge variants (strict, chaldean, pythagorean, vedic, numks). The only differentiator offered is the system name embedded in the purpose sentence, which is implied rather than presented as selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources