explore_bi_wheel
Create an interactive bi-wheel chart comparing two astrological charts. Supports synastry, transit, progressed, return, and solar arc modes; click planets or aspects for interpretations.
Instructions
Generate an interactive bi-wheel chart comparing two astrological chart positions.
CREDIT COST: 2 credits per call for most modes (1 per wheel computed); solar_return/lunar_return modes cost 6 (5 for the return + 1 for the natal wheel).
The inner wheel is always Person 1's natal chart. The outer ring depends on mode: • synastry — Person 2's natal chart (needs Person 2's own birthplace). • transit — Transiting planets for a given date. • progressed — Secondary progressed positions (person2_datetime = target date). • solar_return — Nearest solar return chart (person2_datetime = year to return for). • lunar_return — Nearest lunar return chart (person2_datetime = target month). • solar_arc — Solar arc directed positions (person2_datetime = target date). Cross-aspects are drawn as coloured dashed lines; click any planet, aspect line, or house cusp for interpretation. Prefer this whenever the user should SEE the comparison — it renders interactively in MCP Apps hosts and falls back to static SVG elsewhere. For raw synastry data without a visual, use ephemeris_synastry.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Chart comparison mode. Defaults to 'synastry'. | |
| location | No | Person 1 / Natal location. Prefer a plain place name like 'New York, NY' — resolved via the same lookup `location_search` uses; ambiguous names throw with a disambiguation hint. Supplied person1_latitude/person1_longitude win. | |
| person1_name | No | Display name for Person 1 / Natal chart (e.g. 'Alice'). Used in the badge and summary. | |
| person2_name | No | Display name for Person 2 (synastry mode). Used in the badge and summary. | |
| person1_datetime | Yes | Birth datetime for Person 1 / Natal chart. ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`. | |
| person1_latitude | No | Birth latitude for Person 1 (decimal degrees, positive = North). Optional if `location` is a place name — the resolver fills it in. Never recall coordinates from memory. | |
| person1_timezone | No | IANA timezone for Person 1's birth location (e.g. `America/New_York`); required when the datetime is naive. | |
| person2_datetime | Yes | Datetime for the outer wheel. Meaning depends on mode: synastry = Person 2 birth datetime; transit/progressed/solar_arc = target date; solar_return/lunar_return = any date within the target year/month. ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`. | |
| person2_latitude | No | Birth latitude for Person 2. REQUIRED in synastry unless `person2_location` is given — never inferred from Person 1. Other modes default to Person 1's coords. | |
| person2_location | No | Person 2 / outer-chart place name, resolved like `location`. person2_latitude/person2_longitude win. | |
| person2_timezone | No | IANA timezone for Person 2 / the outer chart (e.g. `America/Chicago`); required when the datetime is naive. | |
| person1_longitude | No | Birth longitude for Person 1 (decimal degrees, positive = East). Optional if `location` is a place name. | |
| person2_longitude | No | Birth longitude for Person 2. REQUIRED in synastry unless `person2_location` is given. Other modes default to Person 1's coords. |