Skip to main content
Glama

Find busy times on Google Calendar

find_google_calendar_busy_times
Read-only

Return the busy blocks across one or more calendars so a free slot can be proposed. Returns times only, never event titles.

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": {
      "mailbox": "<mailbox>"
    },
    "name": "find_google_calendar_busy_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesEmail address of the connected Gmail/Google Workspace mailbox to act on. Call list_authorized_mailboxes to see available options.
timeMaxNo
timeMinNo
calendarIdsNoCalendars to check. Defaults to the primary calendar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond that: the output is times only and never exposes event titles, which matters for privacy/format expectations. It says nothing about pagination, time-range defaults, or permission requirements.

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?

Two short sentences, front-loaded with the operation and its purpose, with zero filler. Every clause earns its place.

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

Completeness3/5

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

With no output schema, the description does some of the return-value work by stating that only times are returned. But it leaves the timeMin/timeMax semantics and default range unspecified, which an agent needs in order to call this correctly for a scheduling query.

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

Parameters2/5

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

Schema coverage is 50%: mailbox and calendarIds are documented (including the default to primary calendar), but timeMin and timeMax are bare strings with no format hint, and the description never mentions the time window at all. For a tool whose core query is a time range, the description fails to compensate for the undocumented half of the parameters.

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

Purpose4/5

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

States a specific verb and resource ('Return the busy blocks across one or more calendars') and the second sentence implicitly separates it from event-listing siblings by declaring it returns times only, never titles. It stops short of naming list_google_calendar_events or find_outlook_calendar_busy_times explicitly, so the differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

'so a free slot can be proposed' implies the scheduling/free-busy use case, which is genuine usage context. However, there is no explicit when-to-use-vs-alternative guidance (e.g., versus list_google_calendar_events or search_google_calendar_events) and no stated prerequisites or exclusions.

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