Timezone Lookup by City or Country Code

omnial/x402-timezone-lookup

Given a city name or a 2-letter country code, returns the location's IANA timezone, its current UTC offset and abbreviation, whether daylight saving time is in effect, and the current local time. A latitude,longitude pair is accepted but did not resolve in testing (Tokyo's coordinates came back unresolved). A query that does not resolve to a known location comes back as a normal result with `found: false` and an explanation, not an error.

activeper callv5

Price

Up to $0.0325 per call; you pay what the call used

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.00.

Data source

IANA Time Zone Database

Data from the IANA Time Zone Database.

Use it

Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

For developers: the calls your assistant makes

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/x402-timezone-lookup" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/x402-timezone-lookup" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/x402-timezone-lookup", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/x402-timezone-lookup", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0325

Updated: Oct 27, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "A city name or a 2-letter country code. A latitude,longitude pair is accepted but did not resolve in testing."
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "properties": {
    "error": {
      "type": "string",
      "description": "A human-readable explanation, present only when the query did not resolve to a known location, suggesting a country code, city name, or coordinates instead."
    },
    "found": {
      "type": "boolean",
      "description": "Present and `false` when the query did not resolve to a known location (observed on a coordinate-pair query). Not present at all on a resolved lookup -- treat its absence as a successful resolution, not as `found: true` implied."
    },
    "query": {
      "type": "string",
      "description": "The query text exactly as submitted, echoed back."
    },
    "is_dst": {
      "type": "boolean",
      "description": "Whether daylight saving time is currently in effect. Only observed on a resolved lookup."
    },
    "timezone": {
      "type": [
        "string",
        "null"
      ],
      "description": "The IANA timezone name, e.g. 'Europe/London'. Observed `null` when the query does not resolve."
    },
    "utc_offset": {
      "type": "string",
      "description": "e.g. 'UTC+1'. Only observed on a resolved lookup."
    },
    "abbreviation": {
      "type": "string",
      "description": "e.g. 'GMT+1'. Only observed on a resolved lookup."
    },
    "country_code": {
      "type": "string",
      "description": "2-letter country code of the resolved location. Only observed on a resolved lookup."
    },
    "utc_offset_hours": {
      "type": "number",
      "description": "The same offset as a plain number of hours. Only observed on a resolved lookup."
    },
    "current_local_time": {
      "type": "string",
      "description": "The current local time at the resolved location, e.g. '09/19/2026, 08:33:32 GMT+1'. Only observed on a resolved lookup."
    }
  },
  "description": "The timezone lookup result.",
  "additionalProperties": true
}