Numerology Compatibility
asterwise_get_numerology_compatibility
Compares two people on Pythagorean Life Path numbers derived from their names and birth dates and returns a score, tier label, narrative, strengths, challenges, and advice.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
person1_name | string | yes | First person's full name. |
person1_date | string | yes | First person's date of birth, YYYY-MM-DD. |
person2_name | string | yes | Second person's full name. |
person2_date | string | yes | Second person's date of birth, YYYY-MM-DD. |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Pairwise numerology only — no charts, rashis, or kootas. Outputs discrete compatibility_score 1..10 with textual bands. It does not run asterwise_get_compatibility (Jyotish matchmaking) or regional porutham tools.
Workflow
BEFORE: RECOMMENDED — asterwise_get_numerology_profile per person — sanity-check Life Paths before comparing.
AFTER: None.
Input
Four strings (two names, two dates) are passed through without local guards.
Output contract
data.life_path_1 (int)
data.life_path_2 (int)
data.compatibility_score (int — 1 through 10)
data.compatibility_level (string — 'Excellent', 'Good', 'Average', or 'Challenging')
data.interpretation (string)
data.strengths[] (string array)
data.challenges[] (string array)
data.advice (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
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:
— For Vedic matching, use asterwise_get_compatibility instead.
Do not confuse with
asterwise_get_compatibility — sidereal koota scoring, not numerology integers.
asterwise_get_numerology_profile — single-person profile, not dyad scoring.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.