Free MCP tool
resolve_timezone
Resolve a city or region before generating a bodygraph, so an agent can move from conversational location input to a stable timezone identifier.
Developer outcome: Less client-side geocoding logic and fewer invalid timezone inputs.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | Yes | City, region, or place to resolve, such as Bristol, UK. |
lang | string | No | Preferred ISO language code for display labels; defaults to English. |
Request
Sanitized JSON-RPC
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "resolve_timezone",
"arguments": {
"query": "Bristol, UK"
}
}
}Success response shape
- Matched location names
- IANA timezone identifiers
- Coordinates for disambiguation
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
- Invalid or empty query
- No matching location
Quota behavior
This lookup is non-consuming. An authorized call uses zero API units and does not change the calculation quota. Tier, validation, and rate-limit checks still apply.