Asterwise

Soul Urge Number

asterwise_get_soul_urge_number

Read-onlyIdempotent

Calculates the Soul Urge (Heart's Desire) number from vowels in the full name. Only A, E, I, O, U are treated as vowels — Y is always a consonant in this system. Reduces each name part separately before summing, preserving master numbers 11, 22, 33.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_personality_number — complete the name number trinity.

INPUT CONTRACT: name — Full legal name as used at birth. Example: 'Arjun Mehta', 'Sofia Rossi' Y is always treated as a consonant — not a vowel.

DO NOT CONFUSE WITH: asterwise_get_expression_number — all letters, not vowels only. asterwise_get_personality_number — consonants only, not vowels.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-soul-urge-number/

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>"
    },
    "name": "asterwise_get_soul_urge_number"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Full legal name as used at birth, all parts; its letters are converted to numerology values.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; its letters are converted to numerology values."New value: +"Full legal name as used at birth, all parts; its letters are converted to numerology values."

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; letters are converted to numerology values."New value: +"Person's full name as commonly written; its letters are converted to numerology values."

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / name / description

Added value: +"Person's full name as commonly written; letters are converted to numerology values."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "name",
-  "response_format"
-]New value: +[
+  "name"
+]
```
AddedMay 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral detail beyond that: only A/E/I/O/U count as vowels, Y is a consonant, each name part is reduced separately before summing, and master numbers 11/22/33 are preserved. It doesn't cover failure modes directly, but defers to a documented error contract.

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?

Front-loaded with the calculation, then scoped by labelled WORKFLOW / INPUT CONTRACT / DO NOT CONFUSE WITH blocks, which makes it easy to scan. Slight redundancy: the 'Y is always a consonant' rule is stated twice in close succession, and the external docs link is long. Efficient overall, but not maximally tight.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and the description correctly spends its budget on computation semantics, workflow placement and sibling disambiguation instead. For a low-complexity, two-parameter derived-number tool, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3 and the schema already documents both parameters. The description still adds value with concrete example values ('Arjun Mehta', 'Sofia Rossi') and an explicit caveat that Y must be treated as a consonant when supplying the name, which is a semantic constraint not present in the schema.

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?

States a specific verb (calculates) and a specific resource (Soul Urge / Heart's Desire number), and immediately pins the distinguishing rule: vowels only, with Y always a consonant. It also explicitly names the sibling tools it must not be confused with, so an agent can separate it from asterwise_get_expression_number and asterwise_get_personality_number without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing: BEFORE is None (standalone), AFTER is asterwise_get_personality_number 'to complete the name number trinity'. The DO NOT CONFUSE WITH block names two alternatives and states the exact rule that selects each (all letters vs. consonants only). This is when-to-use and when-not-to-use guidance in full.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?