Nextmail

Delete calendar

deleteCalendar

Destructive

Delete a calendar you keep. Deleting a calendar deletes the events in it. Unless notifyGuests is false, everyone invited to an upcoming meeting you organised in it is sent a cancellation from the address that invited them, as Cancel meeting does. A meeting that came in through a calendar import is cancelled quietly unless notifyGuests is true. Your default calendar cannot be deleted. A to-do list goes with its to-dos. For a calendar you are a member of, you leave it, it stays with its keeper and nobody is told. A chat always asks first.

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": {
      "id": "<id>"
    },
    "name": "deleteCalendar"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	A calendar id, `cln_` followed by 24 hex characters, as the list of calendars shows it.
`notifyGuests`	No	false deletes the calendar without telling anyone. Left out or true, the guests of every upcoming meeting you organised in it are sent a cancellation, and true tells the guests of imported meetings too.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / notifyGuests

Added value: +{
+  "description": "false deletes the calendar without telling anyone. Left out or true, the guests of every upcoming meeting you organised in it are sent a cancellation, and true tells the guests of imported meetings too.",
+  "type": "boolean"
+}

AddedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the destructive annotation: event deletion, guest cancellation emails, quiet cancellation for imported meetings, default-calendar protection, to-do deletion, membership leave semantics, and chat confirmation. These are exactly the consequences an agent needs before invoking a destructive tool.

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?

Front-loads the core action and consequence, then adds necessary edge cases. It is somewhat long and reads as a dense paragraph, but most sentences carry distinct destructive-behavior information.

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

Completeness5/5

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

Given a destructive calendar deletion with no output schema, the description covers the important consequences, notification nuances, and protected/default cases. An agent has enough context to avoid surprising destructive behavior.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents id and notifyGuests. The description still adds useful meaning, especially the default notification behavior, imported-meeting handling, sender address, and comparison to Cancel meeting.

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?

States a specific verb and resource: deleting a calendar, and immediately clarifies that its events are deleted too. This clearly separates it from event-level deletion and covers owned, imported, member, to-do, and chat calendar cases.

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?

Gives clear conditions and exclusions: default calendars cannot be deleted, member calendars are left rather than destroyed, and chat calendars prompt first. It does not explicitly name alternative tools such as removeCalendarMember, so it is strong but not fully routing-oriented.

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

All Nextmail tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.