Skip to main content
Glama

calendar check availability

calendar_check_availability
Read-onlyIdempotent

Query free/busy blocks across one or more calendars for a specified time window to find open meeting slots. Returns availability data so you can schedule without conflicts.

Instructions

Query free/busy blocks for one or more calendars in a time window.

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

Input Schema

NameRequiredDescriptionDefault
time_maxYes
time_minYes
time_zoneNoUTC
calendar_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds that the response is aggregated free/busy blocks rather than event details, which is genuinely useful context, but it omits what happens when calendar_ids is omitted and gives no auth or rate-limit context.

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?

A single front-loaded sentence with no filler and no redundancy. Its brevity is efficient, though it is under-specified rather than tight.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, with four parameters at 0% schema coverage and no usage or input-format guidance, the description leaves an agent without enough information to fill the required time_min/time_max fields reliably.

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 description coverage is 0%, so the schema supplies only bare titles ("Time Min", "Time Max", "Time Zone", "Calendar Ids") with no formats. The description partially compensates by implying calendar_ids means one or more calendars and that time_min/time_max bound a window, but it never specifies datetime format, time zone behavior, or whether a null calendar_ids means all calendars.

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 states a specific verb and resource ("Query free/busy blocks for one or more calendars") plus a scope ("in a time window"). The free/busy framing distinguishes it conceptually from calendar_list_events, but it never names a sibling or explicitly contrasts with event-listing, so it stops short of a 5.

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 when-to-use guidance, no when-not-to-use, and no mention of alternatives such as calendar_list_events for detailed event data. The use case (checking availability before scheduling) is only implied by the tool name, not the description.

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