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

icloud-calendar-mcp

by IceyWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_conflicts

Read-onlyIdempotent

Identify time conflicts by checking for overlapping events in an iCloud calendar. Specify a date range, timezone, and optionally exclude an event to find scheduling clashes.

Instructions

Find overlapping iCloud events

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": {
      "calendar_id": "<calendar_id>",
      "end": "<end>",
      "start": "<start>",
      "timezone": "<timezone>"
    },
    "name": "find_conflicts"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
timezoneYes
calendar_idYes
exclude_event_handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. However, the description adds no behavioral context beyond the name—it does not specify what the function returns (e.g., list of conflicting events) or behavior with no conflicts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence), but at the cost of missing essential details. While there is no fluff, the brevity leaves the agent underinformed. A balanced approach would add parameter context without excessive length.

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 has five parameters, no output schema, and no parameter descriptions, the description is insufficient. It does not specify return format, parameter constraints, or edge cases. The missing information limits the agent's ability to use the tool correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning no parameter descriptions exist in the schema. The description fails to compensate: it does not explain any of the five parameters (start, end, timezone, calendar_id, exclude_event_handle). The agent must guess meanings from parameter names alone.

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 'Find overlapping iCloud events' uses a specific verb and resource, clearly distinguishing the tool from siblings like list_events (which lists all events) and free_busy (which shows availability). It directly conveys the conflict-detection purpose.

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 scenarios like 'before creating an event' or contrast with free_busy. The agent must infer usage context from the tool name alone.

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