Skip to main content
Glama

Create announcement

bb_create_announcement

Create a course announcement with optional start and end dates for scheduled visibility. Requires write access, confirmation, and an instructor role.

Instructions

Create a course announcement, optionally scheduled with start/end dates. 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>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "bb_create_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHTML body
titleYes
confirmNo
endDateNoISO date to stop showing it
courseIdYes
startDateNoISO date to begin showing it

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 non-read-only, non-idempotent, non-destructive behavior. The description adds value beyond that by disclosing the write-gate flag, the required confirm:true acknowledgement, and the instructor-role authorization need.

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?

Single front-loaded sentence, no filler — the action and optional scheduling come first, prerequisites second.

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 6-parameter mutation with no output schema, the prerequisites and scheduling semantics are covered, but the description leaves unclear what a successful call returns and how courseId should be formatted.

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 50%, and the description clarifies that startDate/endDate are scheduling windows and that confirm must be true. It says nothing about courseId format or title/body constraints, so half the parameters remain undocumented.

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 ("Create a course announcement") plus the optional scheduling scope via start/end dates. An agent can tell it apart from the update/delete announcement siblings, though it does not name them explicitly.

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 real prerequisites (BB_ALLOW_WRITES=1, confirm:true, instructor role), which is useful when-to-use context. It does not say when to prefer bb_update_announcement over this tool, or what to do for announcements that already exist.

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