Skip to main content
Glama

Read discussion replies

bb_get_discussion_thread
Read-only

Retrieves every reply in a specified Blackboard discussion thread using course, forum, and message IDs so you can review the full conversation.

Instructions

Read every reply to one discussion thread.

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>"
    },
    "name": "bb_get_discussion_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdNo
forumIdYes
courseIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — that it returns 'every' reply, implying an exhaustive, non-paginated read — but says nothing about permissions, ordering, or what happens with a thread that has no replies.

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?

A single front-loaded sentence with zero filler. It is terse to the point of being thin, but no wording needs to be removed.

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 tool with three required IDs, an undocumented optional boardId, no output schema, and 0% schema coverage, one sentence is not enough to call it correctly. The description should at minimum clarify the relationship among courseId, forumId, boardId, and messageId.

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% for four parameters, and the description mentions none of them, so it provides no compensation. The most confusing case, boardId alongside forumId and courseId (which appears optional relative to the required three), is completely unaddressed.

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 ('Read') and a precisely scoped resource ('every reply to one discussion thread'), which distinguishes it reasonably well from bb_get_discussion and bb_create_discussion_thread. It stops short of naming a sibling explicitly, so the boundary with bb_get_discussion (thread body vs. replies) is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no mention of when to prefer bb_get_discussion or bb_get_discussion_thread over this tool. The only guidance is what the purpose sentence implies.

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