Skip to main content
Glama

Find Meeting Times

find_meeting_availability
Read-only

Find meeting time suggestions where all participants are free, ranked by confidence, within a specified window and duration. Suggests slots only; use create_event to book.

Instructions

Find meeting time suggestions where all participants are free, ranked by confidence. Searches between after_date_time and before_date_time for a slot of duration_minutes. Read-only: suggests times only — use create_event to book one.

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": {
      "participants": "<participants>",
      "after_date_time": "<after_date_time>",
      "before_date_time": "<before_date_time>"
    },
    "name": "find_meeting_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
participantsYesAttendee email addresses. The signed-in user is automatically the organizer.
max_candidatesNoMax slots to return (default: 3)
after_date_timeYesSearch window start (ISO 8601, e.g. 2026-06-04T00:00:00Z)
before_date_timeYesSearch window end (ISO 8601, e.g. 2026-06-06T00:00:00Z)
duration_minutesNoMeeting length in minutes (default: 30)
is_organizer_optionalNoWhether the organizer's attendance is optional (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces rather than contradicts that, adding the useful trait that results are 'ranked by confidence.' It does not cover what happens when no slot is found or how the max_candidates cap interacts with ranking, but the core behavioral profile is disclosed.

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

Conciseness5/5

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

Three short sentences, front-loaded with purpose, then search mechanics, then the read-only boundary and handoff. Every sentence carries information; no padding.

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?

With six parameters fully documented in the schema and no output schema, the description is nearly sufficient — it even hints at the return content ('suggestions... ranked by confidence'). Minor gaps remain on empty-result behavior and how many candidates come back by default, but nothing blocks correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including defaults and bounds is already documented. The description only restates the window and duration relationship in prose, adding no syntax or format detail beyond the schema — the baseline 3 applies.

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 — 'Find meeting time suggestions' — plus the scope constraint that all participants must be free. It reads clearly as a suggestion-search tool, distinct from the sibling create_event that actually books time.

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?

Explicitly declares read-only behavior ('suggests times only') and names the alternative operationally: 'use create_event to book one.' An agent knows both when to call this and where the boundary is, with nothing left to inference.

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

Deploy Server

Other Tools