Skip to main content
Glama
Sign In
blackboard-mcp

blackboard-mcp

by felipedias-ie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read course discussions

bb_list_discussions
Read-only

Retrieve forum posts and replies for a course discussion using course ID and forum ID. Optionally pass a message ID to view replies to that specific post.

Instructions

Reads a discussion forum: its top-level posts, and the replies to one post when messageId is given. Find the forumId from a "discussion" item in bb_browse_course (its contentDetail carries conferenceId/id).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
forumIdYesForum id, e.g. "_20001_1".
courseIdYesCourse id, e.g. "_12345_1".
messageIdNoRead replies to this post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description explains the conditional behavior driven by messageId and the relationship to bb_browse_course. It does not discuss pagination or default limits, but the read-only safety profile is already covered by annotations.

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 front-loaded sentences with no filler: the first states the operational behavior, the second gives the required lookup path. Every sentence earns its place.

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

Completeness4/5

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

For a read-only list operation with no output schema and an openWorldHint, the description tells the agent what it will get and how to satisfy the required forumId. Minor gaps such as default limit and exact response shape remain, but they are not blocking for correct invocation.

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

Parameters4/5

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

The description adds meaning beyond the schema by explaining that messageId selects the reply view and that forumId should be the conferenceId/id from bb_browse_course. The undocumented limit parameter is not addressed, but three of four parameters already have schema descriptions.

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 uses a specific verb ('Reads') and resource ('discussion forum'), and clearly distinguishes the two call modes: top-level posts by default, or replies when messageId is provided. It does not explicitly name or differentiate a sibling tool such as bb_list_conversations, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

The description gives a concrete prerequisite: obtain forumId from a 'discussion' item in bb_browse_course, including where to find the id (contentDetail conferenceId/id). This is clear usage context, though it does not explicitly state when to choose this tool over sibling read-list tools.

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

Deploy Server

Other Tools