Skip to main content
Glama

Send course message

bb_send_message

Start a new Blackboard conversation with one or more course participants by providing course ID, participant IDs, and message body; writes must be enabled and confirmed.

Instructions

Start a new conversation with one or more course participants. 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": {
      "courseId": "<courseId>",
      "participantIds": "<participantIds>",
      "body": "<body>"
    },
    "name": "bb_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNo
courseIdYes
canBeRepliedToNo
participantIdsYesBlackboard user ids (e.g. _123_1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the generic non-read, non-idempotent, non-destructive profile; the description adds the concrete write-gate and confirmation requirement, which is real operational context an agent would otherwise miss. It stops short of describing failure behavior when the flag is off or what a successful send returns.

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, action first and prerequisites second, with no filler. Every clause carries information the agent needs.

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 five-parameter mutation tool with no output schema and thin schema documentation, the definition covers the gating mechanics but not the meaning of most inputs or what happens on rejection. Adequate to attempt a call, not adequate to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% of five parameters — only participantIds is annotated in the schema. The description clarifies just one parameter (confirm:true) and leaves courseId, body, and canBeRepliedTo entirely unexplained, so it does not compensate 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?

The description states a specific verb and resource ('Start a new conversation') and names the audience ('one or more course participants'). The word 'new' implicitly separates it from bb_reply_message, though 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 Guidelines3/5

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

It gives hard prerequisites (BB_ALLOW_WRITES=1, confirm:true) that gate invocation, which is useful. But it never says when to choose this over bb_reply_message or bb_create_announcement, so usage is only implied.

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