MCP OpsBridge

calendar_find_free_slots

Find mutually free time slots across calendars by providing a time range and duration, enabling quick meeting scheduling.

Instructions

Find mutually available time slots across 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": {
      "time_min": "<time_min>",
      "time_max": "<time_max>"
    },
    "name": "calendar_find_free_slots"
  }
}

Input Schema

Name	Required	Description
`time_max`	Yes	End of search range (ISO 8601)
`time_min`	Yes	Start of search range (ISO 8601)
`calendar_ids`	No	Calendars to check for availability
`duration_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only states the high-level purpose. It does not explain how availability is determined, what the output looks like, how time zones or defaults are handled, or whether it respects calendar permissions.

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, concise sentence that is front-loaded with the key action and object. There is no filler or redundant information.

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?

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the one-line description is insufficient. It does not address return value format, default behavior, timezone considerations, or edge cases, leaving the agent under-informed.

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?

The schema descriptions cover time_min, time_max, and calendar_ids, but duration_minutes lacks a description. The tool description adds no parameter meaning beyond the schema, and the 75% schema coverage is not compensated by any additional explanation.

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 clearly identifies the resource ('mutually available time slots across calendars'). It distinguishes itself from sibling tools like calendar_query_events (which queries events) and calendar_list_calendars (which lists calendars) by focusing on availability across multiple calendars.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or situations where a different calendar tool would be more appropriate.

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