Startup MCP tool
get_transits
Use the contract field `natalChart` to submit the underlying bodygraph data, then request current or dated transit context. The literal identifier is preserved for API compatibility.
Developer outcome: Build time-aware agent experiences without calculating planetary positions in the client.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
date | string (ISO 8601) | No | Transit moment to calculate; defaults to the current time. |
timezone | string | No | IANA timezone for the transit moment. |
natalChart | object | No | Optional bodygraph birth input with birthDateTime and timezone. The field name is part of the backend contract. |
Request
Sanitized JSON-RPC
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "get_transits",
"arguments": {
"date": "2026-08-06T12:00:00Z",
"timezone": "UTC",
"natalChart": {
"birthDateTime": "1990-05-15T14:30:00",
"timezone": "America/New_York"
}
}
}
}Success response shape
- Transit planetary positions
- Activated gates and channels
- Connections to the supplied bodygraph input
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
- Startup tier required
- Invalid bodygraph input
- Invalid transit date
- Quota exceeded
Quota behavior
A successful call consumes one shared API unit. Failed entitlement checks do not run the tool. Check current usage at my.humandesign.ai.