Skip to main content
Glama

Cancel calendar event

event_cancel
DestructiveIdempotent

Cancel an event and remove it from the public page, retaining its record. Ask for confirmation before calling; requires confirm: true. Requires API key scope: draft.

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>",
      "confirm": "<confirm>"
    },
    "name": "event_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds the key nuance that the record is retained and only public visibility is lost, plus the required API key scope ("draft") and the confirmation requirement. It stops short of describing downstream effects (e.g., whether already-scheduled or sent campaigns referencing the event are affected) or the response body.

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?

Three short clauses, front-loaded with the effect, then safety, then auth scope; nothing is redundant with the title and no sentence is wasted.

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 two-parameter mutation with no output schema, the description covers the effect, the guardrail, and the auth scope, which is enough to call it correctly. The only shortfall is that reversibility (how to undo a cancellation, e.g., event_update) and any cascade effects are not addressed.

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 description coverage is 0%, so the description must carry the load; it does so for the non-obvious parameter by stating that confirm must be true, which the bare schema only conveys via a const. The id parameter is only implied ("an event") and its format/constraints come solely from the schema, leaving a small gap.

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?

"Cancel an event and remove it from the public page, retaining its record" gives a specific verb plus resource and even defines the deletion model (unpublish, not hard delete). It implicitly separates itself from event_update by describing an outcome rather than a field edit, but it never names that sibling explicitly.

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?

It states a concrete precondition for calling ("Ask for confirmation before calling; requires confirm: true"), which is real when-to-use guidance. It does not name alternatives such as event_update for cases where the user only wants to hide or edit the event, so the exclusions side is left to inference.

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