Skip to main content
Glama

Coline

Delete event

delete_event
DestructiveIdempotent

Deletes an event from the calendar, or some occurrences of a repeating one. To call off a meeting and tell attendees, cancel it with update_event instead.

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": {
      "workspace": "<workspace>",
      "eventId": "<eventId>"
    },
    "name": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
occurrenceStartNoWhich occurrence, by its start, with recurrenceScope this or following.
recurrenceScopeNoFor a repeating event: this occurrence, this and following, or the whole series.

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is carried structurally. The description still adds genuinely new behavioral context by implying deletion is silent (no attendee notification), which is the distinction that drives the sibling routing. It does not say whether deletion is recoverable, leaving a small gap.

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?

Two sentences, zero filler. The primary action is front-loaded and the routing caveat follows immediately, so the agent gets both the capability and the disambiguation in one pass.

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?

With rich annotations, an output schema, and fully described parameters, the description only needs to cover intent and routing, which it does. The one omission is whether the deletion is permanent or undoable, which matters for a destructive calendar mutation.

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 description coverage is 100%, and the occurrenceStart and recurrenceScope fields already document 'this/following/series'. The description's phrase 'or some occurrences of a repeating one' reinforces the partial-deletion semantics, but adds no syntax or value constraints 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 (deletes) and resource (an event from the calendar), and adds the scope nuance that it can remove only some occurrences of a repeating event. It explicitly separates itself from the update_event sibling, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Provides an explicit when-not rule with a named alternative: if the intent is to call off a meeting and notify attendees, use update_event instead. That is the exact confusion an agent would otherwise have with a destructive delete on a calendar object.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources