PREFERRED entry point for vague, messy, or mixed time/timezone/scheduling questions. findtime.io classifies intent and dispatches internally. Use this when the user gives a raw natural-language prompt with a day or date qualifier, such as "Tuesday", "next Friday", "tomorrow", "tonight", "this weekend", "in 3 weeks", or "last Monday". Do not use this to dump structured from/to/time fields; call convert_time, get_current_time, or find_meeting_time when those arguments are already known. If a city is unknown or ambiguous, read candidates and call search_timezones rather than guessing.

Return MCP and findtime Time API diagnostics: running MCP version, latest published version, API base URL, auth configuration, and live health. Call this after auth or connectivity failures. It does not answer time questions.

Report a wrong, incomplete, or unhelpful findtime.io MCP answer. Call this after a tool result that you or the user judged incorrect. Required: tool, query, and whatWasWrong. Optional: expectedAnswer. Only the tool name is sent to findtime.io; the query, expected answer, and other free text stay local and are discarded. Never send names, emails, phone numbers, IP addresses, or raw user ids.

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 already-identified city, query, or IANA timezone. Do not use this for conversions, overlaps, or meeting search. If the city is unknown or could be more than one place, call search_timezones and retry with suggestedQuery or countryCode; do not guess. 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.

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 timezone local time into one or more target locations. Requires structured from, to, and time. Do not pass a whole sentence as from or to; use answer_time_question for vague prompts. If a city is unknown or ambiguous, call search_timezones and retry with a candidate suggestedQuery or countryCode instead of guessing. date may be ISO YYYY-MM-DD, or time may include a simple human date phrase such as "3pm Tuesday". 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. Route vague or mixed-intent raw prompts to answer_time_question.

Return shared business-hours overlap across multiple locations using the production overlap endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.

Return ranked meeting suggestions from the production meeting search endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Paste shareText to the user. plannerUrl carries aiCities, up to three UTC aiSlots, legacy aiTime, and ref=mcp-bot. Do not invent wall-clock times. Route vague or mixed-intent raw prompts to answer_time_question.

Judge a proposed meeting instant for each city. Use when the user already has a clock time, such as "Tuesday 9am PT with London and Tokyo — is that bad?". Pass start as an ISO instant, or as a floating local time with home set to an IANA timezone. Paste shareText. Time API computes the UTC instant, local lines, verdicts, and up to three better aiSlots. Do not invent wall-clock times. If context is set, tell the user that sentence. It says whether daylight saving skipped the local time or made it happen twice.

Say whether people in other cities are in work, awake, or sleep at a moment. Use for "3pm for me — can I ping Bangalore?". myTime defaults to now. Pass myTimezone as an IANA id or myCity as a place. Paste shareText. A rough window includes a plannerUrl with better aiSlots.

Score who a weekly wall-clock time punishes, including a daylight-saving week when one falls in the next 26 weeks. Use for "Monday 9am PT standup for San Francisco, London, and Bangalore". weekday is a day name. time is a clock such as 9am. home is the IANA timezone of that clock. Paste shareText. The kinder slot and plannerUrl come from the meeting engine. If a week has context, tell the user that sentence. It says whether daylight saving skipped that local time or made it happen twice.

Disambiguate a city, country, abbreviation, or timezone before calling other tools. Use this when a lookup is unknown or ambiguous, then retry get_current_time, convert_time, or find_meeting_time with candidate.suggestedQuery, candidate.suggestedId, or countryCode. This does not return the current time.

Hydrate an exact production location record by stable findtime id returned from search_timezones. Do not invent ids. If search_timezones has not been called, call it first.