Skip to main content
Glama

Remove a member

bb_remove_member
Destructive

Remove a user's enrollment from a Blackboard course, requiring write access enabled, confirmation, and course management permission. Use it to unenroll a member.

Instructions

Remove an enrollment from a course. 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>"
    },
    "name": "bb_remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
confirmNo
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely useful context about the write gate, the confirm flag, and the permission needed — but says nothing about side effects, such as what happens to submitted work or grades, or whether the action is reversible.

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 sentences, zero padding, with the action front-loaded and the preconditions following immediately. Everything stated is operationally relevant.

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 destructive, non-idempotent tool with no output schema, the definition covers purpose and preconditions but leaves the consequences of removal and the response behavior unstated. An agent knows how to call it but not fully what it loses.

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 has to compensate. It explains the confirm parameter's meaning and implies both the course and member targets, which loosely covers all three parameters, but adds no format or identifier guidance for courseId/userId.

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?

"Remove an enrollment from a course" gives a specific verb and resource, clearly distinct from the add/update sibling variants. It stops short of naming an explicit alternative, but the destructive verb makes the intent unambiguous.

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?

It states the gating conditions up front: BB_ALLOW_WRITES=1, confirm:true, and course management permission. It does not discuss when to prefer a role change (bb_update_member_role) over outright removal, so there is no explicit alternative routing.

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