Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Check Free/Busy Status

calendar_freebusy_query
Read-onlyIdempotent

Check free/busy availability across multiple calendars to find common free time for meetings.

Instructions

Check availability (free/busy times) for one or more calendars within a time range.

This is useful for finding available meeting times across multiple people. It only returns busy time blocks (not event details) for privacy.

Args:

  • time_min (string): Start of the time range (ISO 8601 format, e.g., '2024-01-15T00:00:00Z')

  • time_max (string): End of the time range (ISO 8601 format, e.g., '2024-01-22T00:00:00Z')

  • calendar_ids (string[]): Array of calendar IDs or email addresses to check (e.g., ['primary', 'colleague@company.com'])

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For each calendar, a list of busy time blocks within the range.

Requirements for checking other people's calendars:

  • Same Google Workspace organization, OR

  • They have shared their calendar with you, OR

  • Their calendar is public

Examples:

  • Check your availability: calendar_ids=["primary"], time_min="2024-01-15T09:00:00Z", time_max="2024-01-15T18:00:00Z"

  • Check team availability: calendar_ids=["alice@company.com", "bob@company.com"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
time_minYesStart of the time range (ISO 8601 format, e.g., '2024-01-15T00:00:00Z')
time_maxYesEnd of the time range (ISO 8601 format, e.g., '2024-01-22T00:00:00Z')
calendar_idsYesArray of calendar IDs or email addresses to check (e.g., ['primary', 'colleague@company.com'])
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds context that only busy blocks are returned (no event details) for privacy, and mentions response format options.

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?

Well-structured with Args section and examples. Information is front-loaded but could be slightly more concise. Every sentence adds value.

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?

No output schema, but description explains return type (list of busy time blocks). Also covers privacy and access requirements. Adequate for the tool's complexity.

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. Description adds examples, ISO 8601 format details, default for response_format, and clarifies calendar_ids accept emails.

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 clearly states the tool checks free/busy availability for calendars within a time range, distinguishing it from sibling tools like calendar_get_event and calendar_list_events which provide event details.

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?

Provides explicit guidance for when to use (finding meeting times across people) and requirements for checking others' calendars (Workspace org, shared, public). Includes examples but does not explicitly state when not to use vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EveryInc/google-workspace-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server