Skip to main content
Glama
Sign In
mjucius

Cozi MCP Server

by mjucius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete an appointment

delete_appointment

Delete an appointment. Returns true on success; errors if the id is not on the (year, month) page. A recurring series (recurring: true in get_calendar) needs scope: 'this' removes only the occurrence on occurrence_day…

Instructions

Delete an appointment. Returns true on success; errors if the id is not on the (year, month) page. A recurring series (recurring: true in get_calendar) needs scope: 'this' removes only the occurrence on occurrence_day, 'this_and_following' ends the series before it, 'series' removes every occurrence, past and future. Confirm a 'series' delete with the user first. Holidays, subscribed calendars and birthdays cannot be deleted.

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
scopeNoRequired for a recurring series: 'this' = only the occurrence on occurrence_day, 'this_and_following' = that occurrence and every later one, 'series' = every occurrence.
notifyNoSend Cozi's change notification to the attendees who have notifications on, like the Cozi app's 'notify' option. Off by default; only when the user asks for it.
appointment_idYes
occurrence_dayNoWith scope 'this' or 'this_and_following': the occurrence's `day` as get_calendar lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.5.0
    • addedInput schema / properties / notify
      Added value: +{
+  "description": "Send Cozi's change notification to the attendees who have notifications on, like the Cozi app's 'notify' option. Off by default; only when the user asks for it.",
+  "type": "boolean"
+}
    • addedInput schema / properties / occurrence_day
      Added value: +{
+  "description": "With scope 'this' or 'this_and_following': the occurrence's `day` as get_calendar lists it.",
+  "type": "string"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Required for a recurring series: 'this' = only the occurrence on occurrence_day, 'this_and_following' = that occurrence and every later one, 'series' = every occurrence.",
+  "enum": [
+    "this",
+    "this_and_following",
+    "series"
+  ],
+  "type": "string"
+}
  2. First observedv2.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states the return value (true on success), the error condition (id not on the given year/month page), the destructive reach of each scope including that 'series' removes past AND future occurrences, and a required user-confirmation step. Auth/permission requirements are not covered, which keeps it from a 5.

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-loaded with purpose and return behavior, then ordered into recurring semantics, safety confirmation, and exclusions. Every sentence is load-bearing, though the scope enumeration partly duplicates the schema's own enum description.

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 6-parameter destructive tool with no annotations and no output schema, the description covers return behavior, errors, destructive scope variants, a confirmation gate, and blocked entity types. Pairing/auth prerequisites are the main omission.

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 50%, so the baseline is 3. The description does add real value by explaining the coupling of appointment_id with (year, month) — the id must be on that page — and by reinforcing the recurring-only requirement for scope and its link to occurrence_day. It says nothing about notify (covered by the schema) or the year/month value ranges.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Delete an appointment") and adds eligibility rules that distinguish it from update/create siblings by naming what delete cannot touch (holidays, subscribed calendars, birthdays). It does not explicitly name a sibling tool, but the operation is unambiguous.

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 conditional guidance: scope applies to recurring series detected via `recurring: true` in get_calendar, and 'series' deletes require user confirmation first. It also implies a when-not (holidays, subscribed calendars, birthdays). No alternative tool is named for modifying rather than deleting, so it stops short of 5.

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