Skip to main content
Glama

Delete announcement

bb_delete_announcement
Destructive

Deletes a Blackboard course announcement after confirmation; intended for instructors with write access enabled.

Instructions

Delete an announcement. Requires BB_ALLOW_WRITES=1, confirm:true and an instructor role.

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": {
      "courseId": "<courseId>",
      "announcementId": "<announcementId>"
    },
    "name": "bb_delete_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
courseIdYes
announcementIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new operational context beyond that: a write-gate environment flag, an explicit confirmation parameter requirement, and a role prerequisite. It omits what happens on failure or whether the deletion is recoverable, keeping it at 4.

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 action stated first and the prerequisites immediately after. Every clause carries information an agent needs.

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 three-parameter destructive mutation with no output schema, the description covers the critical operational facts: write gate, confirm flag, and required role. What remains missing is failure behavior and recoverability, which matters for a destructive action but is secondary to the prerequisites already stated.

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 0%, so the description must compensate, and it only partially does: it explains that confirm must be true, adding real semantics for that parameter. courseId and announcementId are never discussed, nor is the expected identifier format, leaving two of three parameters explained only by their names.

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?

The description opens with a specific verb+resource ('Delete an announcement'), which pairs with the tool name to make the target unambiguous against siblings like bb_delete_discussion_post or bb_delete_calendar_event. It stops short of naming an alternative to differentiate against, so it lands at 4 rather than 5.

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 gives concrete preconditions for use: BB_ALLOW_WRITES=1, confirm:true, and an instructor role. That is clear context for when the call will succeed. It does not name alternatives or state when not to use this tool (e.g., archive vs. delete), so it falls short of a 5.

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