Skip to main content
Glama

Get group

bb_get_group
Read-only

Fetch a Blackboard course group by course ID and group ID to view its members and shared resources for group review or management.

Instructions

Get one group with its members and shared resources.

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

Input Schema

NameRequiredDescriptionDefault
groupIdYes
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 structurally. The description adds useful behavioral context by disclosing that the response bundles members and shared resources, which is meaningful with no output schema, but it says nothing about permissions, group visibility, or failure behavior for a missing 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 tight sentence with the verb and scope front-loaded and no wasted wording. It is appropriately short for a simple two-parameter read, though brevity here shades into under-specification rather than pure efficiency.

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?

For a simple read-only lookup, annotations cover safety and the description hints at the return contents, which is enough to attempt the call. However, neither parameter is explained anywhere and there is no output schema, so the agent cannot tell what a group identifier looks like or what happens on invalid input.

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?

Interest arises in extracting only the JSON object, not the comprehensive restructuring; this is key tension.

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?

States a specific verb and resource ("Get one group") and adds scope by noting it includes members and shared resources, which tells the agent the payload is richer than a bare group record. It does not distinguish itself from nearby siblings like bb_list_group_members or bb_join_group, so an agent must still infer the boundary.

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 prerequisites, and no mention of any alternative tool or condition that would select this over bb_list_group_members or bb_join_group. The agent is left to infer usage entirely from the name.

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