Name Correction
asterwise_get_name_correction
Scores the current spelling of a personal name against the birth-date Life Path, suggests alternate spellings with harmony metrics, and echoes recommendation stub fields.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | yes | Person's full name as commonly written; letters are converted to numerology values. |
date | string | yes | Date in YYYY-MM-DD format. |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Returns data.current_name metrics (expression, soul urge, personality, master and karmic flags, compatibility band, harmony_score 1..5) plus data.alternatives[] with identical shape per suggestion. data.recommendation is currently null (stub). Empty alternatives[] means no better spelling was found — still success. Not for business entities (asterwise_get_business_name_analysis) or mobile/vehicle checks.
Workflow
BEFORE: RECOMMENDED — asterwise_get_numerology_profile — baseline numbers before renaming advice.
AFTER: None.
Input
name and date strings only; upstream validates.
Output contract
data.full_name (string)
data.birth_date (string)
data.life_path (int)
data.current_name:
name (string)
expression (int)
soul_urge (int)
personality (int)
is_master (bool)
karmic_debt (int or null)
compatibility (string — 'harmonious', 'neutral', or 'challenging')
harmony_score (int — 1 through 5)
data.alternatives[] — objects matching data.current_name shape
data.recommendation (currently null — stub)
Response format
response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.
Compute class
MEDIUM_COMPUTE
Errors
INVALID_PARAMS (local — caught before upstream call):
None — all validation is upstream.
INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Empty alternatives[] is valid when no improvement exists.
Do not confuse with
asterwise_get_business_name_analysis — entity Expression scan, not personal spelling alternatives.
asterwise_get_chaldean_numerology — Chaldean compounds, not harmony-scored spelling list.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.