Skip to main content
Glama

Delete personal calendar event

bb_delete_calendar_event
Destructive

Delete a calendar event you created in Blackboard after enabling write access and confirming the action.

Instructions

Delete an event you created. Requires BB_ALLOW_WRITES=1 and confirm:true.

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": {
      "itemId": "<itemId>"
    },
    "name": "bb_delete_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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, and the description adds real context beyond that: a server-side write gate and a mandatory confirmation flag. It stops short of stating that deletion is permanent or how recurring events are handled.

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 short sentences, zero filler, with the destructive action and the required safeguards front-loaded. Nothing is redundant with the annotations or schema.

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

Completeness3/5

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

For a destructive mutation with annotations covering the safety profile and no output schema, the essentials (auth gate, confirm flag, ownership) are present. Missing are the source/format of itemId and the reversibility or recurrence behavior, which matter 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 coverage is 0%, so the description must carry parameter meaning; it explains that confirm must be true but says nothing about itemId—its format, where to obtain it, or whether it must be an event the caller owns. Half the parameters are clarified, so it partially compensates for the coverage 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?

States a specific verb and resource ('Delete an event') and adds an ownership scope ('you created') that meaningfully narrows the operation. It is distinguishable from the create/update calendar siblings, though the resource is named only as 'event', leaving 'calendar' to the tool name and title.

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

Usage Guidelines3/5

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

Gives concrete preconditions (BB_ALLOW_WRITES=1 and confirm:true) and an implicit eligibility rule (only events you created). It does not address when to use this instead of bb_update_calendar_event or what to do if the event is not yours, so guidance is clear but incomplete.

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