generate_composite_chart
Generate individual chart data and the combined relationship dynamics for two people from a single tool call.
Developer outcome: Let an agent reason over relationship mechanics using consistent structured data.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
personA | object | Yes | First person's ISO date and IANA timezone. |
personB | object | Yes | Second person's ISO date and IANA timezone. |
idempotencyKey | string | Yes | Stable key for this intended composite calculation. Reuse it only with identical arguments when retrying. |
Birth times are local wall clock times. Send the birth date and time as it read on the clock where the person was born, with no Z and no UTC offset, and give the timezone separately as an IANA identifier. "birthDateTime": "1990-05-15T14:30:00" with "timezone": "America/New_York" means half past two in the afternoon in New York.
Deprecated: Values ending in Z or a numeric offset are deprecated. The MCP forwards them and the API still accepts them for now, reading them as UTC, and the deprecation is announced on the API response. They will stop being accepted, and the date will be announced in advance. Read the full rule.
Request
Sanitized JSON-RPC
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "generate_composite_chart",
"arguments": {
"personA": {
"birthDateTime": "1990-05-15T14:30:00",
"timezone": "America/New_York"
},
"personB": {
"birthDateTime": "1988-11-02T08:15:00",
"timezone": "Europe/London"
},
"idempotencyKey": "composite-example-v1"
}
}
}Success response shape
- Both individual bodygraphs
- Combined centers, channels, and electromagnetic connections
- Relationship-level structured metadata
The response also includes tier and quota metadata supplied by the API entitlement layer. Exact domain fields vary by tool and requested detail level.
Errors
- Missing person input
- Invalid date or timezone
- Quota exceeded
Quota behavior
After input validation, authorization, and tier checks pass, an execution attempt that reaches the calculation provider consumes exactly one shared API unit—even if a later presentation step fails. Malformed or ambiguous input, denied tiers, unknown references, and other pre-provider failures consume zero. Check current usage at my.humandesign.ai.