Skip to main content
Glama

Reply to discussion thread

bb_reply_to_discussion

Posts a reply to an existing Blackboard discussion message using course, forum, and message IDs; requires write access enabled and explicit confirmation.

Instructions

Reply to an existing discussion post. 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>",
      "messageId": "<messageId>",
      "body": "<body>"
    },
    "name": "bb_reply_to_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
boardIdNo
confirmNo
forumIdYes
courseIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write-but-not-destructive profile is covered. The description usefully adds the gating requirement that writes must be enabled and confirm:true supplied — context annotations cannot express. It does not explain what confirm does or warn that repeated calls create duplicate replies despite non-idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action first and the precondition second; nothing is wasted. The terse phrasing is efficient, though the second sentence could tie 'confirm' explicitly to the parameter rather than the literal string 'confirm:true'.

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?

This is a mutation tool with six undocumented parameters and no output schema, so the description carries most of the explanatory burden. It covers the write gate but omits identifier semantics, what the reply returns, and error behavior when the write flag is unset — substantial gaps for a mutation.

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 0% across six parameters, so the description must compensate and largely does not. It only clarifies 'confirm', leaving courseId, forumId, messageId, body, and the optional boardId entirely undefined — an agent must guess identifier formats and whether boardId is needed.

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: 'Reply to an existing discussion post.' An agent immediately knows the action and target. It does not, however, distinguish this from the nearby bb_reply_message or bb_create_discussion_thread siblings, so the boundary is left ambiguous.

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 implied by the phrase 'existing discussion post,' which tells the agent a thread must already exist, and the environment precondition (BB_ALLOW_WRITES=1, confirm:true) is stated. There is no explicit when-not guidance and no named alternative for replying to a message versus a discussion post.

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