Lo Shu Grid
asterwise_get_lo_shu_grid
Derives a Lo Shu three-by-three frequency grid from birth-date digits and annotates planes, missing or repeated digits, and per-digit traits.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | yes | |
response_format | enum: markdown, json | no |
What it covers
Chinese Lo Shu analysis: counts how often each digit one through nine appears in the date string, lays counts into the classical magic-square positions, and adds plane_analysis plus number_analysis entries keyed by digit strings '1'..'9'. Zero digits are ignored for placement. It does not compute Pythagorean Life Path (asterwise_get_numerology_profile) or Chaldean compounds.
Workflow
BEFORE: None — standalone.
AFTER: None.
Input
date string only; validated upstream.
Output contract
data.birth_date (string)
data.grid — three-by-three nested int array (row-major):
row positions map to numbers [4,9,2], [3,5,7], [8,1,6] respectively; cell value = count of that digit in the date (0 if absent)
data.present_numbers[] (int array)
data.missing_numbers[] (int array)
data.repeated_numbers[] (int array — digits appearing at least twice)
data.plane_analysis:
thought_plane — { numbers[] (int array), description (string), complete (bool) }
will_plane — same shape
action_plane — same shape
golden_yod — same shape
silver_yod — same shape
data.number_analysis{} — keys '1' through '9' (string keys):
count (int)
plane (string)
trait (string)
status (string — 'missing', 'present', or 'strong')
note (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:
— Zeros in ISO dates are skipped — only digits one through nine populate the grid.
Do not confuse with
asterwise_get_numerology_profile — letter-based Western numbers, not digit-frequency Lo Shu.
asterwise_get_name_correction — spelling harmonics, not birth-date grids.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.