Skip to main content
Glama

Join a group

bb_join_group
Idempotent

Join a self sign-up group in a Blackboard course using course and group IDs. Requires BB_ALLOW_WRITES=1 and confirm:true.

Instructions

Join a group that offers self sign-up. Requires BB_ALLOW_WRITES=1 and confirm:true. Experimental: Blackboard may restrict self-enrolment to the web UI.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
groupIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive mutation; the description adds real value on top by disclosing the write-flag environment requirement, the mandatory confirm flag, and an experimental caveat about server-side restrictions. It stops short of 5 because it does not say what happens on repeat calls or what a rejected self-enrolment looks like.

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?

Three short clauses, front-loaded with the purpose, then the gating requirements, then the caveat. Every sentence adds information an agent needs before calling, and nothing is repeated from the title or schema.

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 simple three-parameter mutation with no output schema, the definition covers the main failure modes (writes disabled, missing confirm, server-side restriction). The only gap is what a successful join returns or changes for the caller, which an agent must infer.

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 description coverage is 0%, so the description carries the burden: it clarifies that confirm must be true, which is the least obvious of the three parameters. courseId and groupId are left entirely to their names, so the description only partially compensates for the missing schema documentation.

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 ("Join a group") and immediately narrows the scope to groups offering self sign-up, which distinguishes it from membership-management siblings like bb_add_member. It does not explicitly name a sibling alternative, so it stops short of a 5.

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?

Gives concrete preconditions for invocation (BB_ALLOW_WRITES=1 and confirm:true) and warns that self-enrolment may be restricted to the web UI, which tells the agent when this call will fail. It does not point to an alternative tool for cases where self sign-up is unavailable.

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