Skip to main content
Glama

List group members

bb_list_group_members
Read-only

Retrieve all members of a specific Blackboard course group using the course ID and group ID.

Instructions

List members of one group.

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

Input Schema

NameRequiredDescriptionDefault
groupIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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 nothing beyond that — no indication of whether results are paginated, how large a group listing can be, whether membership data includes roles, or whether the caller must already be a member of the group.

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 short sentence with no filler, and the resource scope is front-loaded. It is efficient but so terse that the brevity shades into under-specification rather than crispness.

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 two-parameter read tool with annotations covering safety and no output schema, the remaining burden is explaining the parameters and the result shape, and the description does neither. An agent knows the gist but not how to interpret courseId or what the member list contains.

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%, so both required parameters rest entirely on their names. The description clarifies only that groupId selects "one group"; it says nothing about what courseId is for or why a group lookup needs a course context, which is exactly the kind of detail the bare schema cannot supply.

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 members") scoped to "one group," which is unambiguous on its own. It does not distinguish itself from nearby siblings such as bb_list_roster or bb_list_group_members-style alternatives, so an agent must infer the boundary from names alone.

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 guidance, no exclusions, and no mention of when an agent should prefer this over bb_list_roster or bb_get_group. Usage is only implied by the tool name and the words "one group."

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