Skip to main content
Glama

Read discussion threads

bb_get_discussion
Read-only

Reads discussion forum threads with top-level posts, authors, bodies, and reply counts to help review or summarize course discussions.

Instructions

Read the threads (top-level posts) in a discussion forum, with authors, bodies and reply counts.

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_get_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdNoBoard id; defaults to "default"
forumIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 useful content about what comes back (authors, bodies, reply counts), which matters because there is no output schema, but it says nothing about pagination, result limits, or whether bodies are truncated.

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?

A single tight sentence that front-loads the action and scope, then lists the return contents. No filler or redundant restatement of the title.

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

Completeness3/5

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

Because there is no output schema, the brief mention of authors, bodies, and reply counts is valuable, but two of three parameters are undocumented and there is no indication of result size or pagination. For a listing tool this leaves meaningful gaps.

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 33% — only boardId is documented (defaults to "default"), while forumId and courseId are bare strings. The description does not compensate, giving no hint about where forumId comes from, its format, or the boardId default behavior.

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 names a specific verb and resource: read the threads (top-level posts) in a discussion forum, and clarifies that only top-level posts are returned. It implicitly separates this from bb_get_discussion_thread by scoping to the listing level, though it never names that sibling.

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: an agent can infer this is the listing call and bb_get_discussion_thread is the single-thread call, but nothing states when to choose one over the other. No prerequisites, pagination guidance, or exclusions are given.

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