workspace-mcp

Query Freebusy

query_freebusy

Read-onlyIdempotent

Retrieve free/busy status for one or more Google Calendar IDs over a given time range.

Instructions

Returns free/busy information for a set of calendars.

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": {
      "user_google_email": "<user_google_email>",
      "time_min": "<time_min>",
      "time_max": "<time_max>"
    },
    "name": "query_freebusy"
  }
}

Input Schema

Name	Required	Description
`user_google_email`	Yes	The user's Google email address. Required.
`time_min`	Yes	The start of the interval for the query in RFC3339 format (e.g., '2024-05-12T10:00:00Z' or '2024-05-12').
`time_max`	Yes	The end of the interval for the query in RFC3339 format (e.g., '2024-05-12T18:00:00Z' or '2024-05-12').
`calendar_ids`	No	List of calendar identifiers to query. If not provided, queries the primary calendar. Use 'primary' for the user's primary calendar or specific calendar IDs obtained from `list_calendars`.
`group_expansion_max`	No	Maximum number of calendar identifiers to be provided for a single group. Optional. An error is returned for a group with more members than this value. Maximum value is 100.
`calendar_expansion_max`	No	Maximum number of calendars for which FreeBusy information is to be provided. Optional. Maximum value is 50.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.21.3Jun 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already provide the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds the basic output scope ('free/busy information for a set of calendars'). However, it does not disclose limitations such as expansion caps, auth prerequisites, or the fact that detailed event data is not returned.

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?

The description is a single, front-loaded sentence with no filler or redundancy. Every word contributes to the core meaning, and it is appropriately sized for the tool's simplicity.

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?

The description, complemented by a 100%-covered input schema and an output schema, is sufficient for an agent to invoke the tool correctly. The only notable gap is the absence of usage guidance versus sibling tools, but that is already captured in the usage dimension.

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 the input schema fully documents all six parameters including defaults, formats, and maximum values. The description adds no parameter-level meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

The description uses a specific verb ('Returns') and resource ('free/busy information for a set of calendars'), making the core purpose clear. It does not explicitly differentiate itself from siblings like get_events, so it misses the top score.

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?

The description gives no guidance about when to use this tool versus alternatives such as get_events or list_calendars. There is no mention of availability checking, exclusions, or conditions that would select this tool.

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

Deploy Server