Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

delete_event

Permanently delete a calendar event by its unique ID. This action is irreversible and removes the event completely.

Instructions

Permanently delete a calendar event by ID. This action cannot be undone. Example: {"id":"ghi09876"} → "deleted". Side effects: destructive, irreversible. The first call deletes; subsequent calls with the same id error.

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

Input Schema

NameRequiredDescriptionDefault
idYesUUID of the event to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / id / description
      Added value: +"UUID of the event to delete."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Explicitly notes destructive, irreversible side effects and that subsequent calls with the same ID error. Since no annotations are provided, the description fully covers behavioral traits.

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 sentences with no waste: purpose, irreversibility warning, example and side effect. Front-loaded with core action.

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

Completeness5/5

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

For a simple one-parameter tool with no annotations or output schema, the description covers purpose, side effects, example, and error behavior. Complete enough for correct invocation.

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%, so baseline is 3. Description adds an example but does not provide additional semantics beyond the schema's description of 'UUID of the event to delete'.

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?

Clearly states 'Permanently delete a calendar event by ID', specifying verb and resource. Distinguishes from sibling tools like create_event, update_event, list_events, and delete_memo/todo.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like update_event for cancellation. Only mentions irreversibility, but does not provide context for selection.

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