Numerology Profile
asterwise_get_numerology_profile
Builds a Pythagorean numerology profile from a legal name and birth date and returns core numbers, cycles, lucky digits, and summary copy.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | yes | Person's full name as commonly written; its 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
Computes Life Path, Expression, Soul Urge, Personality, Birthday, Pinnacles, Challenges, lucky_numbers[], summary, and key_traits via the upstream profile engine. data.personal_year is currently null — use asterwise_get_personal_year for the dedicated Personal Year endpoint. It is not Chaldean mapping (asterwise_get_chaldean_numerology), Lo Shu grids (asterwise_get_lo_shu_grid), or paired compatibility (asterwise_get_numerology_compatibility).
Workflow
BEFORE: None — this tool is standalone.
AFTER: asterwise_get_personal_year — fills Personal Year when needed.
Input
name and date strings are forwarded without extra local validation; malformed payloads fail upstream.
Output contract
For each of data.life_path, data.expression, data.soul_urge, data.personality, data.birth_day:
number (int, or a string like '13/4' when a karmic debt is present)
reduced_number (int)
is_master_number (bool)
is_karmic_debt (bool)
karmic_debt_number (int or null — 13/14/16/19 met anywhere in the reduction; when present, number is a string like '13/4')
interpretation (string)
keywords[] (string array)
data.personal_year — currently null — use asterwise_get_personal_year for Personal Year calculation
data.birth_day is the day of the month as a core number: the 11th/22nd stay master 11/22, the 29th is 11; the 13th/14th/16th/19th carry that karmic debt (number '13/4', karmic_debt_number 13)
data.pinnacles[] — four objects: number (int — 1-9, 11, 22 or 33), start_age (int), end_age (int), interpretation (string), focus_areas[] (string array); the first ends at 36 − Life Path (a master Life Path counted as its digit)
data.challenges[] — four objects with the same shape as pinnacles[]; number is 0-8
data.lucky_numbers[] (int array — no repeats: first the Life Path, Expression, Soul Urge, Personality and Birth Day (these may be master numbers 11, 22, 33; a master Birth Day appears as 11 or 22), then digits 1-9 from the birth date in ascending order, topped up with unused digits 1-9 (at most 9 are guaranteed); never 0 or other two-digit numbers)
data.summary (string)
data.key_traits[] (string array)
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):
— 422 validation_error with details[].issue = no_letters when the name has no letters A-Z (e.g. '123', '!!!', or a name written only in a non-Latin script) — ask the user for the name spelled in Latin letters; this is not a server fault.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— personal_year field is null here by design.
Do not confuse with
asterwise_get_chaldean_numerology — Chaldean letter values and compound structure, not Pythagorean cores.
asterwise_get_lucky_numbers — lightweight lucky list without the full profile payload.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.