Asterwise

Numerology Compatibility

asterwise_get_numerology_compatibility

Read-onlyIdempotent

Compares two people on their Pythagorean Life Path numbers, worked out from their birth dates. Returns a score, tier label, narrative, strengths, challenges, and advice.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile per person — sanity-check Life Paths before comparing. AFTER: None.

INPUT CONTRACT: Four strings (two names, two dates) are passed through without local guards. The API requires both names, but they do not change the score: only the birth dates do.

DO NOT CONFUSE WITH: asterwise_get_compatibility — sidereal koota scoring, not numerology integers. asterwise_get_numerology_profile — single-person profile, not dyad scoring.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-numerology-compatibility/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`person1_date`	Yes	First person's date of birth, YYYY-MM-DD.
`person1_name`	Yes	First person's full name. The API requires it, but it does not change the score: compatibility compares the two Life Path numbers from the birth dates.
`person2_date`	Yes	Second person's date of birth, YYYY-MM-DD.
`person2_name`	Yes	Second person's full name. The API requires it, but it does not change the score: compatibility compares the two Life Path numbers from the birth dates.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / person1_name / description

Previous value: -"First person's full name."New value: +"First person's full name. The API requires it, but it does not change the score: compatibility compares the two Life Path numbers from the birth dates."

changedInput schema / properties / person2_name / description

Previous value: -"Second person's full name."New value: +"Second person's full name. The API requires it, but it does not change the score: compatibility compares the two Life Path numbers from the birth dates."

Changed5 schema fields changedSep 5, 2026
- addedInput schema / properties / person1_date / description
```
Added value: +"First person's date of birth, YYYY-MM-DD."
```
- addedInput schema / properties / person1_name / description
```
Added value: +"First person's full name."
```
- addedInput schema / properties / person2_date / description
```
Added value: +"Second person's date of birth, YYYY-MM-DD."
```
- addedInput schema / properties / person2_name / description
```
Added value: +"Second person's full name."
```
- addedInput schema / properties / response_format / description
```
Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
```

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "person1_name",
-  "person1_date",
-  "person2_name",
-  "person2_date",
-  "response_format"
-]New value: +[
+  "person1_name",
+  "person1_date",
+  "person2_name",
+  "person2_date"
+]

First observedApr 22, 2026

TDQS

Score is being calculated.

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?