Skip to main content
Glama

calendar_check_availability

Read-onlyIdempotent

Check when you have free time in the connected calendar (Google, Outlook or a CalDAV calendar). Shows busy periods and free slots in a given time range. Useful for finding meeting times or checking schedule conflicts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_timeNoEnd date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to end of start_time day, or 7 days from now.
timezoneNoIANA timezone (e.g. 'Asia/Bishkek') that start_time/end_time WITHOUT an offset are in, and that the free slots are reported in. OMIT for UTC.
account_idNoCalendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used.
start_timeNoStart date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to start of today.
calendar_idNoCalendar ID to check. OMIT to use the agent's configured default calendar (or primary).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
working_hours_onlyNoIf true, only show free slots during working hours (9 AM - 6 PM). OMIT to show all free time (the default).
min_duration_minutesNoMinimum duration in minutes for free slots. Filters out short gaps. Default: 30 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used."New value: +"Calendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used."
  2. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.",
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA timezone (e.g. 'Asia/Bishkek') that start_time/end_time WITHOUT an offset are in, and that the free slots are reported in. OMIT for UTC.",
      +  "type": "string"
      +}
  5. Added
  6. Removed
  7. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID to check. Defaults to primary calendar."New value: +"Calendar ID to check. OMIT to use the agent's configured default calendar (or primary)."
  8. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. Because there is no output schema, the description's statement that it shows busy periods and free slots is genuinely useful return-value context, but it doesn't describe the shape of that output or how conflicts are resolved, leaving the behavioral picture only partly filled in.

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?

Three short sentences with the core capability front-loaded and no filler or repetition. The provider list and the 'useful for' sentence each carry some weight, though the latter is the softest part.

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?

With eight optional parameters fully described in the schema and rich annotations covering the read-only safety profile, the description only needs to establish purpose and the nature of the result, which it does. No output schema exists, so a little more on the returned slot structure would make it fully self-sufficient.

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%, and every parameter—time range, timezone, account/calendar targeting, working_hours_only, min_duration_minutes, in_workspace—is documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 for a fully documented schema 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 names a specific verb and resource: checking free time in a connected calendar across Google, Outlook, or CalDAV, and states it 'Shows busy periods and free slots in a given time range.' That is concrete enough for an agent to know what it does. It stops short of a 5 because it never contrasts itself with the sibling calendar_list_events, which also reads the calendar.

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?

It supplies clear usage context: 'Useful for finding meeting times or checking schedule conflicts,' which tells the agent the scenario this serves. It offers no exclusions or named alternatives (e.g., when to prefer listing events), so it sits at 'clear context, no exclusions' rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.