Skip to main content
Glama

Find meeting times

calendar_find_meeting_times
Read-onlyIdempotent

Suggests slots of duration_minutes inside the window when you (across every calendar) and the attendees are free. Slots can fall at night or at weekends unless you pass working_hours_only: true, which most meeting requests want. Only accounts with the calendar.attendee_free_busy capability (see accounts_list) can see other people's time; an attendee none of them can see is left out of the slots and named in warnings with ATTENDEE_NOT_VISIBLE, so tell the user the slot is unconfirmed for that person. Use it before calendar_create_event when the user says "find a time". Times are ISO 8601: with an offset (2026-11-02T09:00:00+02:00), or without one to mean time_zone; all-day events use dates, and their end is the day after the last day. Example: { "duration_minutes": 30, "start": "2026-11-03", "end": "2026-11-06", "attendees": ["ana@contoso.example.com"], "working_hours_only": true }.

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_minutes": "<duration_minutes>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_find_meeting_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesWindow end (exclusive): ISO 8601 date-time or date.
limitNoHow many slots, 1–20 (default 5).
startYesWindow start: ISO 8601 date-time or date.
attendeesNoOther people's email addresses who must be free (up to 20). Anyone your accounts cannot see is ignored and named in `warnings`.
time_zoneNoIANA time zone for dates in and out, e.g. "Africa/Johannesburg". Defaults to the workspace time zone, which prubex_overview returns as `time_zone`.
profile_idNoOnly accounts in this profile (`prf_…` from profiles_list).
account_idsNoOnly these accounts (`acc_…`). Omit to cover every account you can reach.
duration_minutesYesHow long the meeting is.
working_hours_onlyNoOnly within your mailbox's working hours (else Monday to Friday 08:00–18:00 in `time_zone`). Default false: slots can fall at night or at weekends.

Output Schema

NameRequiredDescriptionDefault
slotsYes
warningsNoAccounts that failed or timed out, and attendees no account could see (ATTENDEE_NOT_VISIBLE); everything else is still here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the `calendar.attendee_free_busy` capability prerequisite, the degradation path when an attendee is invisible (omitted from slots, named in `warnings` with ATTENDEE_NOT_VISIBLE, and explicitly unconfirmed), and that slots can land at night or on weekends by default. These are exactly the operational facts an agent cannot infer from structured fields.

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?

Purpose and scope are front-loaded, and the paragraphs proceed from what it does, to defaults, to capability caveats, to sequencing. It is on the long side for a single tool and repeats the `working_hours_only` semantics already in the schema, but nearly every sentence carries actionable content.

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 a 9-parameter scheduling query with an output schema, the description covers the remaining burden: input time formats, timezone resolution, account/profile scoping via sibling tools, partial-visibility warnings, and where it sits in the create-event workflow. Nothing an agent needs 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 the baseline is 3; the description still earns a bump by giving ISO 8601 acceptance rules (offset vs. `time_zone`, date-only form), the all-day `end` = day-after convention, and a worked example object. Some content (the `working_hours_only` default and its fallback window) merely restates the schema, keeping it off a 5.

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 ('Suggests slots of `duration_minutes` inside the window when you ... and the `attendees` are free') and pins the scope to 'across every calendar'. It also positions itself relative to `calendar_create_event`, so an agent can distinguish it from the mutation sibling without opening the schema.

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

Usage Guidelines4/5

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

Gives a concrete trigger ('Use it before calendar_create_event when the user says "find a time"') and advises passing `working_hours_only: true` for 'most meeting requests'. It never states when not to use it — e.g. when raw busy blocks from `calendar_get_free_busy` are wanted instead — so the guidance is clear but not exhaustive.

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