Lucky Numbers
asterwise_get_lucky_numbers
Fetches condensed lucky-number guidance for a name and birth date including primary and secondary picks, power number, interpretation, and a date_specific flag.
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
Thin numerology endpoint mirroring lucky_numbers[] from the full profile but omitting pinnacles, challenges, and long interpretations. data.date_specific is always false (profile-derived). Use when payload size matters. It is not the full profile (asterwise_get_numerology_profile) nor Lo Shu counts (asterwise_get_lo_shu_grid).
Workflow
BEFORE: None — standalone.
AFTER: asterwise_get_numerology_profile — if deeper context is required.
Input
name and date forwarded upstream without local checks.
Output contract
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.power_number (int — Life Path anchor)
data.date_specific (bool — always false; derived from profile)
data.interpretation (string)
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
FAST_LOOKUP
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:
— Duplicates asterwise_get_numerology_profile lucky list — choose this tool for smaller JSON only.
Do not confuse with
asterwise_get_numerology_profile — full multi-section profile, not lucky-number-only payload.
asterwise_get_number_meaning — dictionary entry for one integer, not personalised lucky sets.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.