PREFERRED entry point for time/timezone/scheduling questions. findtime.io classifies intent and dispatches internally. Use this WHENEVER the user's input includes a natural-language day or date qualifier, such as "Tuesday", "next Friday", "tomorrow", "tonight", "this weekend", "in 3 weeks", or "last Monday". The specific tools (convert_time, get_current_time, find_meeting_time, etc.) will silently drop these qualifiers if you dispatch to them without an explicit ISO date. Also the right choice for vague or mixed-intent prompts.

Return MCP and findtime Time API diagnostics, including the running MCP version, latest published MCP version, API base URL, auth configuration, and a live health check.

Return enterprise-friendly findtime.io MCP usage help, including supported time-intelligence intents, answer API examples, ambiguity handling examples, and recommended answer-only deployment guidance.

Return the production time snapshot payload for one location or a list of locations.

Return the production current time payload for a single city, query, or timezone. Exact country-name queries may be retried through a canonical city when the resolver can do so deterministically. For relative-date inputs ("Tuesday", "next Friday", "tomorrow", "tonight"), route to answer_time_question, which resolves the relative date and dispatches internally.

Return the production DST schedule payload, including current abbreviation and transition details. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.

Convert a source local time into one or more target locations using the production conversion endpoint. Use ONLY when date is an explicit ISO calendar date (YYYY-MM-DD) you can pass in, OR the conversion is for the current moment with no date qualifier at all. DO NOT use this tool if the user said "Tuesday", "tomorrow", "next Friday", or any other relative day/date phrase; those qualifiers will be silently dropped here. Route to answer_time_question instead, which parses relative dates correctly. When presenting results, copy localTime.weekday, localTime.date, localTime.time12h/time24h, timezone abbreviation, and UTC offset exactly from the tool output; do not recompute or shift day names during synthesis.

Return shared business-hours overlap across multiple locations using the production overlap endpoint. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.

Return ranked meeting suggestions from the production meeting search endpoint. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.

Search production location records by city, country, or timezone-related query.

Hydrate an exact production location record by stable findtime id.