@mnicole-dev/calcom-mcp-server

delete-out-of-office

Remove an out-of-office entry using its ID. Clean up your Cal.com schedule by deleting obsolete or incorrect out-of-office periods.

Instructions

Delete an out-of-office entry by ID.

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": {
      "outOfOfficeId": "<outOfOfficeId>"
    },
    "name": "delete-out-of-office"
  }
}

Input Schema

Name	Required	Description	Default
`outOfOfficeId`	Yes	The out-of-office entry ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It only restates the destructive action without disclosing whether deletion is permanent, what side effects occur, whether authorization is required, or what the response looks like.

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, front-loaded sentence with no filler. Every word contributes meaning and nothing extraneous is present.

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

Completeness3/5

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

For a one-parameter delete with full schema coverage, this is adequate for basic invocation. However, with no annotations and no output schema, the description leaves post-conditions and safety-related context unexplained.

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?

The schema already fully documents outOfOfficeId with 100% coverage. The description's 'by ID' aligns with the parameter but adds no additional semantic detail such as where the ID comes from or how to obtain it.

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 states a specific verb (delete), a specific resource (out-of-office entry), and the key mechanism (by ID). This clearly distinguishes it from sibling tools like create-out-of-office, list-out-of-office, delete-schedule, and delete-event-type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied by the verb and resource: use this when an out-of-office entry needs to be deleted by ID. However, there is no explicit guidance about when not to use it or which sibling tools to prefer for related operations.

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