Skip to main content
Glama
Sign In
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

by conorbronsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

calendar_freebusy_query

Read-only

Check availability by querying free/busy status for one or more calendars over a specified time range, returning busy and free intervals to help schedule meetings.

Instructions

Query free/busy information for one or more calendars over a time range.

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": {
      "timeMin": "<timeMin>",
      "timeMax": "<timeMax>",
      "items": "<items>"
    },
    "name": "calendar_freebusy_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesCalendars/groups to query, as JSON array string, e.g. '[{"id":"primary"}]'
timeMaxYesEnd of the interval, RFC3339 timestamp
timeMinYesStart of the interval, RFC3339 timestamp (e.g. "2026-03-10T00:00:00Z")
timeZoneNoIANA time zone for the response (e.g. "America/Los_Angeles")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so the description only reinforces that this is a read-only availability query. It does not disclose extra behavioral context such as response shape, pagination, or whether external calendar data may appear, but the read-only safety profile is already covered by annotations.

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?

A single, front-loaded sentence states the verb, resource, scope, and time constraint with no filler. Every part of the sentence 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?

For a read-only tool with four fully documented parameters and a short description, the core call is clear. However, the lack of usage differentiation from calendar siblings and the absence of any indication about the free/busy response format leave some gaps, especially since no output schema exists to fill them.

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 coverage is 100%, with field descriptions for items, timeMin, timeMax, and timeZone including examples. The description adds the concept of querying multiple calendars, but the parameters' meaning and format are already well documented in the schema, so the baseline of 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?

The description uses a specific verb 'Query' with a clear resource: free/busy information for one or more calendars over a time range. This distinguishes it from calendar_events_get and calendar_events_list, which fetch event details rather than availability data.

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

Usage Guidelines2/5

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

There is no explicit guidance about when to use this tool instead of calendar_events_get or calendar_events_list. The agent must infer its role solely from the name and the one-line description, with no stated exclusions or alternatives.

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