Skip to main content
Glama

Create discussion thread

bb_create_discussion_thread

Create a new discussion thread in a Blackboard forum where students can post. Provide course ID, forum ID, subject, and body to publish, with write access and confirmation enabled.

Instructions

Start a new thread in a forum where students may create threads. 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>",
      "forumId": "<forumId>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "bb_create_discussion_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThread body (plain text or HTML)
boardIdNo
confirmNo
forumIdYes
subjectYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the write profile is known. The description adds genuinely new operational context that annotations cannot carry: the BB_ALLOW_WRITES=1 environment gate and the required confirm:true flag, which explain why a call may be rejected. It stops short of describing failure modes or what a successful call 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 with no filler. The core action comes first and the prerequisites follow, which is the right ordering for an agent scanning the definition.

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

Completeness2/5

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

For a six-parameter mutation tool with no output schema and near-zero schema documentation, the description should explain the identifier parameters and what success looks like. It covers the write gate but leaves most parameters and the response behavior unaddressed, so an agent cannot confidently construct a call from this alone.

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 17%: body is documented, but courseId, forumId, boardId, subject, and confirm carry no schema descriptions. The description only partially compensates by clarifying that confirm must be true; it says nothing about how forumId relates to boardId, or which identifier selects the target forum.

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 gives a specific verb and resource ("Start a new thread in a forum") and adds a scoping qualifier that it only works in forums where students may create threads. That is enough to separate it from reply-style siblings, though it never names an alternative 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?

Usage is only implied: the reader learns the thread must go in a student-creatable forum, but there is no explicit when-to-use guidance and no statement of when to prefer bb_reply_to_discussion or bb_create_announcement instead. The precondition is a constraint, not routing guidance.

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