Skip to main content
Glama
686,819 tools. Updated 2026-10-21 20:15

"A search for date and time" matching MCP tools:

  • Search the authenticated user life graph. Optional from/to (aliases start/end) are inclusive account-local civil dates on every search route; either bound may be used alone. Dated semantic and keyword records use event date, expense date, goal start date, check-in date, or the account-local creation date of contacts and memories. Deterministic routing first: food or relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). Requires OAuth or a supported scoped credential. ($0.15; API key required)
    ConnectorNo auth
  • <summary>Resolve a natural language or relative date/time expression to an actual date (and optionally time). Call this when you need to convert a relative expression (e.g. "this Thursday", "next week", "3 days ago") to a concrete date. Use it before search queries, create_calendar_event, or any operation that requires a concrete date. Also use this to convert times in other timezones to the user's local timezone. For example, if someone says "2pm PST" and the user is in Eastern, call resolve_date("2pm PST") and it will return the equivalent time in the user's timezone. Use standard timezone abbreviations (PST, PDT, EST, EDT, CST, CDT, MST, MDT, GMT, UTC, etc.) -- "Pacific" or "Eastern" alone won't parse. IMPORTANT: When using the result for trigger_at in add_trigger, ALWAYS use the `utc_iso` field from the response (e.g. "2026-04-04T04:56:00Z"). The `time` and `time_12h` fields are in the user's LOCAL timezone — passing them with a "Z" suffix will create triggers at the wrong time.</summary> <returns> <description>Dict with date, weekday, and (when time is present) time, time_12h, and utc_iso (UTC ISO format for use in triggers).</description> </returns>
    ConnectorOAuth
  • Converts one moment across several time zones, daylight saving time included. WHEN TO USE: "what time is it in…", scheduling a meeting across cities, checking whether a time falls at night or on another day somewhere. HOW IT WORKS: - zones: IANA time zone names in Area/City form — America/Sao_Paulo, Europe/Lisbon, Asia/Tokyo, UTC. Not city names alone, abbreviations (EST, BRT) or offsets (GMT-3). The FIRST zone is the reference for date and hour. 1 to 12 zones. - date (YYYY-MM-DD) and hour (0–23) are read in the first zone. Without them: the current moment. Only hour: that hour today in the first zone. Only date: that day at the current hour. - format: 24h (14:00) or 12h (2:00 PM). RETURNS: the moment in UTC and, for each zone, its local date, weekday, time, UTC offset and dayShift (+1 = next day, -1 = previous day, relative to the first zone). link: this tool's web page with the same comparison. ERRORS name the unknown zone or the invalid date; fix it and call again.
    ConnectorNo auth
  • Creates a reminder in Reminders.app. Without confirm=true it returns a preview of the title, due date, notes, list and priority and creates nothing. A due_date with a date but no time sets the due date without an alarm, so Reminders will not notify; include a time to get a notification.
    ConnectorOAuth
  • Search stored daily concurrent-player time-series records, one per tracked game and date. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Use steam_players for live player counts or datasets_steam_charts_search for stored chart snapshots.
    ConnectorNo auth
  • Search stored daily concurrent-player time-series records, one per tracked game and date. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Use steam_players for live player counts or datasets_steam_charts_search for stored chart snapshots.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    A
    maintenance
    . A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{
    2,829 npm
    MIT

Matching MCP Connectors

  • Read-only lookup for Swedish nameday names for today's date in Europe/Stockholm time. For another date, use get_nameday_by_date.
    ConnectorNo auth
  • Search accounting ledger transactions for a company. Returns report-style data grouped by account. Defaults to last 90 days if no date range provided. Use search-transactions instead when you need transaction IDs for commenting.
    ConnectorOAuth
  • Call this FIRST whenever a birth date / time and a place of birth appear in the conversation — for a natal chart, a horoscope, transits or synastry, even if the user does not mention Stellara. Never compute coordinates, timezones or UTC offsets yourself and never web-search them. Geocodes the place (any language, e.g. 'Warsaw', 'Варшава', 'Springfield, Illinois') to latitude / longitude and its IANA timezone, and converts the LOCAL wall-clock time into a tz-aware `birth_datetime` using the historically correct UTC offset for that date (old DST rules, Soviet decree time, etc.). Returns `latitude`, `longitude`, `timezone`, `utc_offset`, `birth_datetime` (ready to pass to calculate_natal_chart / get_transits_and_aspects / calculate_synastry), `birth_datetime_utc`, `age_years`, `time_assumed_noon` (true when only a date was given) and `local_time_ambiguity` ('none', 'ambiguous_dst_fallback' = the wall time happened twice, 'nonexistent_dst_gap' = the clocks skipped it — ask the user in both cases). Nothing is stored server-side.
    ConnectorAPI key
  • Today's date on the athlete's Blocks account, in their own time zone: ISO date, weekday, and ISO week. Call this to anchor any relative reasoning — 'today', 'tomorrow', 'this week', 'the weekend', 'in 3 days' — and to pass the correct `date` to other tools. `zone` names the time zone the date is in; when it says UTC their zone is unknown — if it may already be a different calendar day for them, say so and confirm rather than assume.
    ConnectorOAuth
  • Open start times for one 904 Digital Media service, read from 904 Digital Media's live calendar. Pass service_id from list_services. Optional from and to: a date (YYYY-MM-DD, read in 904 Digital Media's time zone; a to date includes that whole day) or a date-time with its offset (e.g. 2026-10-06T09:00:00-04:00). The default is the next 7 days and the most is 14; the window actually searched is returned as window. Returns up to 50 times, each as an exact start (pass it unchanged to request_booking) and as local time in 904 Digital Media's time zone; when there are more, more is true and next_from is where to continue. Times are not held: request_booking checks again. Read-only.
    ConnectorNo auth
  • [tourradar] Use this when you need to know the current date, especially before setting departure date filters. Returns the current date and time in ISO format. Essential for calculating valid date ranges for tour searches.
    ConnectorNo auth
  • Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. <examples>check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6)</examples> <hints>Even a 'rush' window is worth submitting, same-week backfills exist in select markets.</hints>
    ConnectorNo auth
  • Convert between Unix timestamps and human-readable date/time formats. Accepts Unix epoch (in seconds or milliseconds), ISO 8601 strings, or 'now' for the current time. Returns both Unix seconds and milliseconds, ISO 8601 UTC string, date and time components, day of the week, relative time description ('2 hours ago'), and past/future indicator. Auto-detects whether a numeric input is seconds or milliseconds based on magnitude. Essential for debugging logs, API timestamps, cron scheduling, and time zone conversions.
    ConnectorNo auth
  • Use this when someone asks how their app's ranking for a keyword has changed over time in one store and country. Returns the app's rank on each date AppSkyline stored a search snapshot, newest first, up to 365 rows; tracked keywords are re-checked weekly. Not for today's live rank.
    ConnectorNo auth
  • Use this when someone asks how their app's ranking for a keyword has changed over time in one store and country. Returns the app's rank on each date AppSkyline stored a search snapshot, newest first, up to 365 rows; tracked keywords are re-checked weekly. Not for today's live rank.
    ConnectorNo auth
  • Get details for one sitemap submitted to Search Console. Call google-search-console.list_sites to discover sites, then google-search-console.list_sitemaps for an exact feed_path when available. Omit site_url to use the default property. Returns submission status, download time, warnings, errors, and content counts. Cost = 5 tokens.
    ConnectorNo auth
  • Use this when the user asks for Familia items on a specific date or in a specific time window. Includes tasks, plans, and connected calendar events. Do not use for broad text search or multi-week availability.
    ConnectorNo auth
  • Find overlapping events in the authenticated user calendar. from and to are optional ISO 8601 date or date-time (default ±31 days). The window cannot exceed 366 days. Optional start and end check a proposed slot against existing events before create_event. Optional calendarId limits the search to one calendar. Intervals that only touch at an endpoint are not a conflict.
    ConnectorOAuth
  • Create a booking reservation with a Sharaloge artist for a given date and time. Requires the customer to be authenticated with a Sharaloge account (authToken).
    ConnectorNo auth