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 | |
date | string | yes | |
response_format | enum: markdown, json | no |
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)
reduced_number (int)
is_master_number (bool)
is_karmic_debt (bool)
karmic_debt_number (int or null)
interpretation (string)
keywords[] (string array)
data.personal_year — currently null — use asterwise_get_personal_year for Personal Year calculation
data.pinnacles[] — four objects: number (int), start_age (int), end_age (int), interpretation (string), focus_areas[] (string array)
data.challenges[] — four objects with the same shape as pinnacles[]
data.lucky_numbers[] (int array)
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):
— 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:
— 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.