Skip to main content
Glama
Sign In
google-calendar-mcp

google-calendar-mcp

by coldinnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_free_time

Find available time slots on a specified date between 8am and 6pm. Specify date and minimum duration to get open intervals.

Instructions

Find available time slots on a given day between 8am and 6pm.

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": {
      "date": "<date>"
    },
    "name": "find_free_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
duration_minutesNoMinimum slot length in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses the time range (8am-6pm) but lacks details on how free slots are computed (e.g., whether existing events are considered, timezone handling, edge cases like no slots). No annotations are provided, so the description carries the burden, but it is only partially transparent.

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?

Single sentence of 10 words, clearly front-loaded with the core action. No unnecessary information; every word contributes meaning.

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?

The tool has no output schema and lacks annotations. The description omits important context such as whether existing events are considered, timezone handling, or what happens when no slots are available. For a 2-parameter tool, more detail is needed for an agent to use it correctly.

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 coverage is 100% with descriptions for both parameters. The description does not add additional meaning to the parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 uses a specific verb 'find' and resource 'available time slots', and includes clear constraints ('on a given day', 'between 8am and 6pm'). This distinguishes it from sibling tools like create_event or list_events, which serve different purposes.

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?

No explicit guidance on when to use this tool vs alternatives. It only implies usage for finding free slots, but does not state when it's appropriate or mention prerequisites like existing events.

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

Deploy Server

Other Tools