Skip to main content
Glama
nityeshaga

google-workspace-mcp-server

by nityeshaga

Check Free/Busy Status

calendar_freebusy_query
Read-onlyIdempotent

Check availability for one or more calendars within a time range to find open meeting slots. Returns busy periods only, preserving privacy.

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_maxYesEnd of the time range (ISO 8601 format, e.g., '2024-01-22T00:00:00Z')
time_minYesStart of the time range (ISO 8601 format, e.g., '2024-01-15T00: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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds privacy behavior ('only returns busy time blocks (not event details)'), permission requirements for other calendars, and the return format. This is useful context beyond the structured 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?

Well-structured with labeled sections (Args, Returns, Requirements, Examples). The main purpose is front-loaded, and every section contributes non-redundant, practical information. Length is appropriate for the tool's complexity.

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?

Despite lacking an output schema, the description clearly explains the return format ('For each calendar, a list of busy time blocks') and permission prerequisites. Examples cover both single and multiple calendar scenarios, making the tool fully actionable.

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 description coverage is 100%, so baseline is 3. The description repeats parameter info but adds value with concrete examples (e.g., ISO 8601 format, calendar ID examples) that clarify real-world usage beyond the schema definitions.

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 opens with a specific verb+resource: 'Check availability (free/busy times) for one or more calendars within a time range.' It clearly distinguishes from sibling tools like calendar_list_events by explicitly noting it returns only busy blocks, not event details, for privacy.

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?

The description states a clear use case: 'useful for finding available meeting times across multiple people.' It also lists permission requirements for checking other people's calendars, giving contextual guidance. It stops short of explicitly naming alternatives or when-not-to-use, which would earn a 5.

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/nityeshaga/google-workspace-mcp-server'

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