Skip to main content
Glama

Change member role

bb_update_member_role
Idempotent

Change a Blackboard course member's role by specifying the course, user, role, and confirmation; write access and course management permission are required.

Instructions

Change a member's course 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_update_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
userIdYesUser id from bb_list_roster
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?

Goes beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing the environment flag and confirmation requirement, plus the permission needed. It does not explain what happens to the member's existing enrollment data or whether the change is reversible, which matters for a role mutation.

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 tight sentences, with the action stated first and the prerequisites immediately after. No filler or redundant restatement of the title.

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 4-parameter mutation with no output schema and low schema coverage, the prerequisites are well covered but the role code meanings and courseId semantics are missing. An agent could call it correctly only if it already knew which role letter to send.

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 coverage is only 25%, so the description needs to carry meaning, and it does explain confirm:true. However, it leaves the role enum values (S, T, P, I, G) completely unexplained — the single most important semantic for a role-change tool — and says nothing about courseId.

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 ('Change a member's course role'), which is clearly distinct from bb_add_member and bb_remove_member. It does not explicitly name those siblings as alternatives, but the action itself is 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?

Gives concrete gating conditions for when the call can succeed: BB_ALLOW_WRITES=1, confirm:true, and course management permission. It lacks explicit exclusions or a pointer to a read-only listing tool for finding valid members, so it stops short of full routing guidance.

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