Skip to main content
Glama

Delete calendar event

delete_calendar_event
Destructive

Remove an event from a project's calendar — every occurrence of it, and every change of one. To take out a single occurrence, cancel it with set_calendar_occurrence instead. Anybody who may write in the project.

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": {
      "project": "<project>",
      "eventId": "<eventId>"
    },
    "name": "delete_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchNoYour own name for a set of changes — e.g. 'solver 2026-11-18' — so rollback_calendar_batch can undo all of them in one call.
sourceNoWho you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway.
eventIdYesThe event, as 'eventId'.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / batch
      Added value: +{
      +  "default": null,
      +  "description": "Your own name for a set of changes — e.g. 'solver 2026-11-18' — so rollback_calendar_batch can undo all of them in one call.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "default": null,
      +  "description": "Who you are, as the history should say it — 'solver', 'bot'. The door (mcp) and your account are recorded anyway.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the crucial extra fact that deletion spans all occurrences and their change history, which the annotations cannot express. It does not say whether the removal is recoverable or what the response contains, but those are modest gaps given the annotation coverage.

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?

Three short sentences, front-loaded with the destructive scope before the alternative and the permission note. The trailing fragment 'Anybody who may write in the project.' is terse but earns its place; no filler.

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, four-parameter tool with no output schema, the description covers scope, the key sibling alternative, and the authorization requirement, which is most of what an agent needs. It leaves the result of the call and any batch/rollback interaction to the schema, a minor but real gap for a delete operation.

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%, with batch, source, eventId, and project all documented in-schema, so the description is not required to explain them. It adds no param-level meaning beyond the schema, which is the correct baseline-3 outcome when the schema does the heavy lifting.

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+resource ('Remove an event from a project's calendar') and immediately qualifies scope: every occurrence and every change of one. This distinguishes it from a single-occurrence removal without the agent needing to open any 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?

Explicitly names the alternative ('To take out a single occurrence, cancel it with set_calendar_occurrence instead') and the condition that selects it, so the agent knows exactly when to route elsewhere. It also states the permission bar ('Anybody who may write in the project'), which tells the caller whether the call is viable at all.

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