Skip to main content
Glama

Find meeting times

find_times
Read-only

Find three chronologically labeled slots; nothing is held. Quote each rationale verbatim; starts_at/ends_at are opaque: never reformat or do timezone math. co_host_emails: members only, never invitees; relay dropped_co_hosts. Card-moved slots are confirmed. Confirmed times are final: never call find_times again to validate, swap, commit or re-render them; search again only if the user asks for different times or a real conflict is returned. Once times are chosen, confirm topic and agenda once, then call propose_meeting. propose_meeting rechecks availability before placing holds. Modes: FRESH searches (per-day counts: ONE call with windows; each call draws a card); SWAP (current_slots + propose_label) re-picks one slot and awaits a yes; COMMIT (current_slots only) finalizes labels. With a card, reply briefly; otherwise list rationale bullets. Overrides, shortfalls and signed_in_as: capable://guide/scheduling.

When to use: Find candidate meeting times.

Example: Find three 30-minute morning slots next week.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "duration_min": "<duration_min>",
      "window_start": "<window_start>",
      "window_end": "<window_end>"
    },
    "name": "find_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowsNoFRESH only: parts inside the window with counts adding up to 3, e.g. Monday 1, Thursday 2.
window_endYesISO 8601 end of the search window.
duration_minYesMeeting duration in minutes (30, 45, 60, or 90).
window_startYesISO 8601 start of the search window.
current_slotsNoThe 3 slots with labels exactly as returned, never reformatted. With propose_label swaps one; alone commits an accepted swap.
propose_labelNoSlot to re-pick (needs current_slots); narrow the window to the user's hint ("Friday morning" → that day 9–12). Not for committing.
co_host_emailsNoWorkspace members who also attend; every host's calendar is intersected. Never the external invitee: pass invitee_timezone instead.
invitee_timezoneNoInvitee IANA timezone (e.g. "Europe/Berlin"); candidates then also fit 9–17 Mon–Fri there. Translate a named city, country or offset; never infer it from an email domain.
target_starts_atNoExact ISO start for the swap (needs current_slots and propose_label). On failure proposed_slot.new is null with target_failure_reason; never substituted.
workday_end_hourNoLatest hour in each host's timezone; omit for saved hours. Only to narrow this search ("mornings only" → 12).
workday_start_hourNoEarliest hour in each host's timezone; omit for saved hours. Only to narrow this search ("after 2pm" → 14). Never saved.

Output Schema

NameRequiredDescriptionDefault
modeNo
noteNo
hostsNo
slotsNo
eventsNo
shortfallNo
timed_outNo
duration_minNo
signed_in_asNo
host_timezoneNo
proposed_slotNo
co_host_noticeNo
dropped_co_hostsNo
invitee_timezoneNo
workday_end_hourNo
workday_start_hourNo
visualization_weeksNo
cohost_busy_intervalsNo
availability_blackoutsNo
display_offset_minutesNo
scheduling_constraintsNo
cohost_blackout_intervalsNo
calendar_context_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / co_host_emails / description
      Previous value: -"Workspace members who also attend; every host's calendar is intersected. Never the external invitee — their availability is unknown by design; pass invitee_timezone instead."New value: +"Workspace members who also attend; every host's calendar is intersected. Never the external invitee: pass invitee_timezone instead."
    • changedInput schema / properties / current_slots / description
      Previous value: -"The 3 committed slots with their labels, exactly as the previous call returned them — never reformat them. With propose_label swaps one; alone commits a previously accepted swap."New value: +"The 3 slots with labels exactly as returned, never reformatted. With propose_label swaps one; alone commits an accepted swap."
    • changedInput schema / properties / invitee_timezone / description
      Previous value: -"IANA timezone of the invitee (e.g. \"Europe/Berlin\"); candidates must then also fall inside 9–17 Mon–Fri there. Translate a city, country or offset the user names; never infer it from an email domain. Omit when it doesn't matter."New value: +"Invitee IANA timezone (e.g. \"Europe/Berlin\"); candidates then also fit 9–17 Mon–Fri there. Translate a named city, country or offset; never infer it from an email domain."
    • changedInput schema / properties / propose_label / description
      Previous value: -"Which committed slot to re-pick (requires current_slots); narrow the window to the user's hint (\"Friday morning\" → that day 9–12). Not for committing — commit with current_slots alone."New value: +"Slot to re-pick (needs current_slots); narrow the window to the user's hint (\"Friday morning\" → that day 9–12). Not for committing."
    • changedInput schema / properties / target_starts_at / description
      Previous value: -"Exact ISO start for the swap's new candidate (requires current_slots and propose_label). Checked against every constraint; on failure proposed_slot.new is null and target_failure_reason says why — it is never silently substituted."New value: +"Exact ISO start for the swap (needs current_slots and propose_label). On failure proposed_slot.new is null with target_failure_reason; never substituted."
    • addedInput schema / properties / windows
      Added value: +{
      +  "description": "FRESH only: parts inside the window with counts adding up to 3, e.g. Monday 1, Thursday 2.",
      +  "items": {
      +    "properties": {
      +      "count": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "window_end": {
      +        "type": "string"
      +      },
      +      "window_start": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "window_start",
      +      "window_end",
      +      "count"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / workday_end_hour / description
      Previous value: -"Latest hour of day in each host's own timezone. Omit to use the saved availability (default 17); pass only to narrow this search (\"mornings only\" → 12)."New value: +"Latest hour in each host's timezone; omit for saved hours. Only to narrow this search (\"mornings only\" → 12)."
    • changedInput schema / properties / workday_start_hour / description
      Previous value: -"Earliest hour of day in each host's own timezone. Omit to use each host's saved availability (default 9); pass only when the user narrows this search (\"mornings only\", \"after 2pm\" → 14). Never persisted."New value: +"Earliest hour in each host's timezone; omit for saved hours. Only to narrow this search (\"after 2pm\" → 14). Never saved."
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed26 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / availability_blackouts / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / availability_blackouts / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / cohost_blackout_intervals / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / cohost_blackout_intervals / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / cohost_busy_intervals / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / cohost_busy_intervals / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / dropped_co_hosts / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / dropped_co_hosts / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / events / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / events / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / invitee_timezone / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / invitee_timezone / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / proposed_slot / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / proposed_slot / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / scheduling_constraints / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / scheduling_constraints / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / shortfall / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / shortfall / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / signed_in_as / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / signed_in_as / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / slots / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / slots / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / visualization_weeks / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / visualization_weeks / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed7 schema fields changed
    • changedInput schema / properties / co_host_emails / description
      Previous value: -"Emails of WORKSPACE MEMBERS who should also attend — everyone's calendars are intersected so the returned slots work for all hosts. WORKSPACE MEMBERS ONLY — never the external invitee: the invitee's availability is unknown by design (that's why you propose three times). If you know the invitee's timezone, pass invitee_timezone instead."New value: +"Workspace members who also attend; every host's calendar is intersected. Never the external invitee — their availability is unknown by design; pass invitee_timezone instead."
    • changedInput schema / properties / current_slots / description
      Previous value: -"The 3 currently-committed slots with their labels. Pass with propose_label to swap one, or ALONE to commit a previously-accepted swap. Use the exact starts_at/ends_at values the previous call returned — never reformat them."New value: +"The 3 committed slots with their labels, exactly as the previous call returned them — never reformat them. With propose_label swaps one; alone commits a previously accepted swap."
    • changedInput schema / properties / invitee_timezone / description
      Previous value: -"IANA timezone of the invitee (e.g. \"Europe/Berlin\"). When set, every candidate must also fall inside 9–17 Mon–Fri in the invitee's local time. Translate from whatever the user says — a city (\"Berlin\" → \"Europe/Berlin\"), a country, an offset — and never infer it from an email domain. Omit when it doesn't matter."New value: +"IANA timezone of the invitee (e.g. \"Europe/Berlin\"); candidates must then also fall inside 9–17 Mon–Fri there. Translate a city, country or offset the user names; never infer it from an email domain. Omit when it doesn't matter."
    • changedInput schema / properties / propose_label / description
      Previous value: -"Which committed slot to re-pick (requires current_slots). Narrow window_start/window_end to the user's hint (\"Friday morning\" → that day 9–12). Do NOT use this to commit — committing is a separate call with current_slots only."New value: +"Which committed slot to re-pick (requires current_slots); narrow the window to the user's hint (\"Friday morning\" → that day 9–12). Not for committing — commit with current_slots alone."
    • changedInput schema / properties / target_starts_at / description
      Previous value: -"Exact ISO start for the swap's new candidate (requires current_slots + propose_label). Validated against every constraint; on failure proposed_slot.new is null and target_failure_reason names why — it is never silently substituted."New value: +"Exact ISO start for the swap's new candidate (requires current_slots and propose_label). Checked against every constraint; on failure proposed_slot.new is null and target_failure_reason says why — it is never silently substituted."
    • changedInput schema / properties / workday_end_hour / description
      Previous value: -"Latest acceptable hour of day, interpreted in each host's own timezone. When omitted, every host's saved availability end hour applies (default 17). Same rule as workday_start_hour: only for momentary narrowing (\"mornings only\" → 12)."New value: +"Latest hour of day in each host's own timezone. Omit to use the saved availability (default 17); pass only to narrow this search (\"mornings only\" → 12)."
    • changedInput schema / properties / workday_start_hour / description
      Previous value: -"Earliest acceptable hour of day, interpreted in each host's own timezone. When omitted, every host's saved availability start hour applies (default 9). Pass explicitly ONLY when the user narrows the moment (\"book mornings only\", \"after 2pm\" → 14) — it overrides the saved hours for THIS search only and is never persisted."New value: +"Earliest hour of day in each host's own timezone. Omit to use each host's saved availability (default 9); pass only when the user narrows this search (\"mornings only\", \"after 2pm\" → 14). Never persisted."
  5. Changed2 schema fields changed
    • addedOutput schema / properties / calendar_context_available
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / scheduling_constraints
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations by disclosing side-effect scope ("nothing is held", propose_meeting rechecks availability before placing holds), state semantics (card-moved slots are confirmed; confirmed times are final), and data-loss behavior (relay dropped_co_hosts). Annotations already cover read-only/non-destructive, so these additions are pure bonus. The only minor opacity is what COMMIT "finalizes labels" actually mutates, which sits slightly awkwardly against readOnlyHint=true but is not a direct contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and nearly every sentence carries an operational rule, but it is a dense run-on paragraph mixing tool behavior, agent reply formatting, and error-handling routing, which makes it harder to parse than it needs to be. It stays compact and wastes little, hence 4 rather than 3.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with three modes, it covers mode selection, edge cases (overrides, shortfalls, dropped co-hosts), and defers the rest to capable://guide/scheduling. An output schema exists, so the absence of return-value prose is not a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: starts_at/ends_at are opaque and must not be reformatted or timezone-adjusted, co_host_emails are members only and never invitees, windows are per-day parts summing to three, and propose_label must narrow the window rather than commit. These are usage rules the schema strings do not carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a specific verb, resource and output shape: "Find three chronologically labeled slots; nothing is held." It also separates the tool from its nearest sibling by naming propose_meeting as the step that actually places holds, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Find candidate meeting times"), explicit when-NOT ("never call find_times again to validate, swap, commit or re-render"), the single re-search condition ("only if the user asks for different times or a real conflict is returned"), and the handoff ("Once times are chosen ... call propose_meeting"). It also enumerates the FRESH/SWAP/COMMIT modes and the parameter combination each requires.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources