Personal Year
asterwise_get_personal_year
Looks up the Personal Year theme for the current calendar cycle from a name and birth date using only month and day inputs server-side.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | yes | Person's full name as commonly written; 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
Endpoint returns Personal Year data derived from birth month/day against the running calendar year on the server — there is no extra year argument in the tool schema. Expected response keys (pending live confirmation): personal_year_number (int), theme (string), interpretation (string), advice (string), favorable_actions[] (string array), challenges[] (string array). asterwise_get_numerology_profile leaves personal_year null; use this tool when Personal Year detail is required.
Workflow
BEFORE: RECOMMENDED — asterwise_get_numerology_profile — see other core numbers first.
AFTER: None.
Input
Only name and date are submitted; the active calendar year is chosen upstream automatically.
Output contract
personal_year_number (int) — expected
theme (string) — expected
interpretation (string) — expected
advice (string) — expected
favorable_actions[] (string array) — expected
challenges[] (string array) — expected
(Schema not yet confirmed from live response; fields above reflect tool design.)
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):
— 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:
— Cannot request arbitrary calendar years via this tool — only the server-selected current year.
Do not confuse with
asterwise_get_numerology_profile — personal_year field there is null; this endpoint supplies the annual theme.
asterwise_get_varshaphal — Vedic solar return, not Pythagorean Personal Year.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.