Skip to main content
Glama

Reply to conversation

bb_reply_message

Posts a reply to an existing Blackboard conversation; requires write access enabled and explicit confirmation.

Instructions

Reply in an existing conversation. 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>",
      "conversationId": "<conversationId>",
      "body": "<body>"
    },
    "name": "bb_reply_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNo
courseIdYes
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive mutation, and the description adds genuinely useful operational context: writes are gated behind BB_ALLOW_WRITES=1 and an explicit confirm:true. It stops short of saying whether the reply notifies participants or what the failure mode looks like, but it goes meaningfully beyond the structured fields.

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 core action first and the gating prerequisites second — nothing superfluous. The terseness is efficient rather than padded, though it leaves no room for the parameter detail the low schema coverage demands.

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 four-parameter mutation with no output schema and zero schema descriptions, the definition is thin. It covers the write-gating requirement but says nothing about the required identifiers or body content, leaving an agent to guess at the most consequential inputs.

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 four parameters, so the description carries the full burden and largely fails. It only mentions confirm (and only that it must be true); courseId, conversationId, and body are left entirely to their names, with no guidance on formats or constraints.

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 (reply) and resource (an existing conversation), which is clear enough to act on. It does not distinguish itself from siblings such as bb_reply_to_discussion or bb_send_message, so an agent must infer which reply/send path applies.

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?

The phrase 'in an existing conversation' implies this is for continuing a thread rather than starting one, and the required confirm:true signals a write-gated flow. However, there is no explicit when-to-use versus bb_send_message or bb_reply_to_discussion, and no statement of what happens when the flag is absent.

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