Skip to main content
Glama

Enroll a member

bb_add_member
Idempotent

Enrolls a user in a Blackboard course with a specified role; requires confirm:true, write access, and course management permission.

Instructions

Enroll a user in a course with a role. Requires BB_ALLOW_WRITES=1, confirm:true and course management permission.

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>",
      "userId": "<userId>",
      "role": "<role>"
    },
    "name": "bb_add_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesS=student, T=instructor, P=teaching assistant, I=instructor, G=grader
userIdYes
confirmNo
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a non-destructive, idempotent write, and the description adds information annotations cannot carry: the environment write-gate flag, the mandatory confirm:true, and the required course-management permission. What it omits is the outcome of a duplicate enrollment and what the call returns, which keeps it from a 5.

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, with the action stated first and the gating requirements second. No filler and nothing buried.

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 write tool with no output schema, the definition covers the invocation gates but not the result: it never says what an enrollment call returns or how a failure (bad courseId, insufficient permission) surfaces. Adequate to call correctly, incomplete for predicting the outcome.

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 only 25%: userId and courseId are bare strings, and confirm has no schema description at all. The description recovers the important piece by stating confirm:true is required, and the role enum is already self-documented in the schema, but the two ID parameters remain unexplained.

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 states a specific verb and resource pair ('Enroll a user in a course') plus the role qualifier, which is enough for an agent to distinguish it from bb_remove_member and bb_update_member_role by name. It stops short of explicitly naming those siblings, so it doesn't reach the top of the scale.

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?

The description gives real preconditions (BB_ALLOW_WRITES=1, confirm:true, course management permission), which tell an agent when the call will succeed. It does not say when to prefer this over bb_update_member_role for an already-enrolled user, so the alternative-selection guidance is only implied.

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