Meeting Time Finder

Find the fairest meeting times across time zones, ranked, with each participant's local time.

Pay by wallet (x402) timezone-meeting-find

Example

Example answer
{
  "timezones": [
    {
      "timezone": "Europe/Stockholm",
      "utc_offset": "UTC+01:00"
    },
    {
      "timezone": "America/New_York",
      "utc_offset": "UTC-04:00"
    },
    {
      "timezone": "Asia/Tokyo",
      "utc_offset": "UTC+09:00"
    }
  ],
  "optimal_slots": [],
  "preferred_hours": "09:00-17:00",
  "duration_minutes": 60,
  "total_viable_slots": 0
}

Inputs

FieldTypeRequiredWhat it is
timezonesarrayYesList of IANA timezone names
preferred_hoursstringNoPreferred hours (e.g. 09:00-17:00)
duration_minutesintegerNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
timezonesarrayAlways (present in every successful answer)
optimal_slotsarrayAlways (present in every successful answer)
total_viable_slotsintegerAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "timezone-meeting-find",
    "inputs": {
      "timezones": [
        "Europe/Stockholm",
        "America/New_York",
        "Asia/Tokyo"
      ]
    },
    "max_price_cents": 3
  }'

Limitations

  • Calendar availability is not considered

    Suggests meeting times based on timezone offsets — does not account for individual calendar availability or local business hour customs

    What to do instead: Use the suggested time window as a starting range and verify with participants' calendar availability