Capable

Find meeting times

find_times

Read-only

Find three chronologically labeled slots; nothing is held yet. Refer to slots by label. Quote each rationale verbatim; starts_at/ends_at are opaque: never reformat or do timezone math. co_host_emails is workspace members only, never invitees (use invitee_timezone); relay dropped_co_hosts. 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; SWAP (current_slots + propose_label) re-picks one slot and awaits a yes; COMMIT (current_slots only) finalizes labels. With a card, reply briefly without listing slots; 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.

Input Schema

Name	Required	Description
`window_end`	Yes	ISO 8601 end of the search window.
`duration_min`	Yes	Meeting duration in minutes (30, 45, 60, or 90).
`window_start`	Yes	ISO 8601 start of the search window.
`current_slots`	No	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.
`propose_label`	No	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.
`co_host_emails`	No	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.
`invitee_timezone`	No	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.
`target_starts_at`	No	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.
`workday_end_hour`	No	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).
`workday_start_hour`	No	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.

Output Schema

Name	Required	Description	Default
`mode`	No
`note`	No
`hosts`	No
`slots`	No
`events`	No
`shortfall`	No
`timed_out`	No
`duration_min`	No
`signed_in_as`	No
`host_timezone`	No
`proposed_slot`	No
`co_host_notice`	No
`dropped_co_hosts`	No
`invitee_timezone`	No
`workday_end_hour`	No
`workday_start_hour`	No
`visualization_weeks`	No
`cohost_busy_intervals`	No
`availability_blackouts`	No
`display_offset_minutes`	No
`scheduling_constraints`	No
`cohost_blackout_intervals`	No
`calendar_context_available`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
Changed26 schema fields changedOct 19, 2026
- 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"
-}
```

Changed7 schema fields changedOct 19, 2026

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."

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / calendar_context_available
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / scheduling_constraints

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/non-idempotent; the description supplies the behavior that matters: nothing is held yet, holds happen later in propose_meeting, dropped_co_hosts must be relayed, and starts_at/ends_at are opaque so no reformatting or timezone math. It also specifies output presentation (card vs. rationale bullets) even though an output schema exists.

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 key constraint (nothing held, quote rationale verbatim) and every sentence carries an operational rule. It is telegraphic and dense — semicolon-chained clauses plus a guide pointer — which costs some readability, but there is little filler.

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

Completeness4/5

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

For a 10-parameter tool with modes, output schema, and destructive downstream steps, it covers state, sequencing, and the main failure path (real conflict → search again; overrides/shortfalls deferred to a guide). The deferral of override and shortfall handling to capable://guide/scheduling leaves a small gap, but nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description still adds mode-level semantics not obvious from the schema — current_slots alone commits, current_slots+propose_label re-picks and awaits a yes, and co_host_emails excludes invitees in favor of invitee_timezone. Most remaining per-parameter detail (hour bounds, target_starts_at failure behavior) is already in the schema, so it does not reach the top band.

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?

States a specific verb and resource with scope: "Find three chronologically labeled slots; nothing is held yet." The contrast with propose_meeting ("propose_meeting rechecks availability before placing holds") makes the boundary unambiguous, which matters given many scheduling siblings.

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 routing rules: use this for candidate times, call propose_meeting once times are chosen, and "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." It also defines the three invocation modes (FRESH / SWAP / COMMIT) and when each applies.

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

All Capable tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?