Skip to main content
Glama

List discussions

bb_list_discussions
Read-only

List a course’s discussion forums with IDs, availability, posting rules, and unread counts, then use each returned forumId to access other discussion tools.

Instructions

List discussion forums in a course with ids, availability, posting rules and unread counts. Use the returned forumId with the other discussion tools.

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

Input Schema

NameRequiredDescriptionDefault
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 genuine context beyond that by enumerating the payload (ids, availability, posting rules, unread counts), but says nothing about pagination, result ordering, or what an empty course returns.

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 short sentences, front-loaded with the action and the returned fields, followed by the forward pointer. No filler or redundancy.

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?

This is a simple single-parameter read tool with no output schema, and the description compensates by naming the fields the agent will get back. The remaining gap is the undocumented courseId origin/format, which is minor for a tool this simple.

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

Parameters3/5

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

Schema coverage is 0% for the single courseId parameter, so the description must carry the burden. 'In a course' loosely implies courseId scopes the query to one course, but it gives no format or provenance for that id (e.g. from bb_list_courses), leaving the only parameter under-explained.

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 ('List discussion forums in a course') and even previews the returned fields (ids, availability, posting rules, unread counts). It doesn't explicitly name a sibling it competes with, but the second sentence routes the agent forward to 'the other discussion tools', which is enough to place it in the workflow.

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?

'Use the returned forumId with the other discussion tools' implies this is a prerequisite/discovery step before bb_create_discussion_thread or bb_edit_discussion_post. That is useful implied guidance, but there is no explicit when-to-use vs when-not framing and no stated preconditions.

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