Skip to main content
Glama

delete_calendar

DestructiveIdempotent

Delete an empty calendar only when confirm=true; refuses calendars with events within 10 years before/after, read-only, subscribed, birthday, or default.

Instructions

Delete an empty calendar. It is refused when the calendar has any event from 10 years back to 10 years ahead, when it is read-only, subscribed or a birthday calendar, and for the default calendar for new events. Events outside that range are not checked. It needs 'confirm' true, also for an empty calendar. Without it, nothing is deleted. The result says what was checked.

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": "<calendar>"
    },
    "name": "delete_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete the calendar. Without it, nothing is deleted.
calendarYesCalendar name or id. Names ignore case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark it destructive and idempotent, but the description adds substantial operational detail: the 10-years-back-to-10-years-ahead event check, unchecked events outside that range, read-only/subscribed/birthday/default calendar refusals, and refusal without confirm. These details materially exceed what the annotations and schema convey.

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?

Front-loads the action, then layers refusal conditions, confirm prerequisite, and result note in a compact sequence. No sentence is filler; the repeated empty-calendar point is purposeful emphasis rather than redundancy.

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

Completeness4/5

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

For a destructive operation with no output schema, it covers the key safeguards, confirm requirement, and event-check range, and notes that the result reports what was checked. It leaves exact return detail and not-found behavior unspecified, which keeps it just short of fully complete.

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%, and the schema already documents both calendar and confirm. The description repeats the confirm requirement and mentions it applies even for an empty calendar, but adds no real syntax or format meaning beyond the schema.

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, 'delete an empty calendar', and narrows scope to empty calendars with named refusal conditions. This clearly separates it from sibling deletions such as delete_event, which would remove an event rather than a calendar.

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 for when deletion is refused and that 'confirm' is mandatory, which effectively defines when the tool can be used. It does not name an alternative such as removing events first or listing calendars, so it stops short of explicit routing.

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