Skip to main content
Glama

Create module or folder

bb_create_module

Creates a module or folder in a Blackboard course outline to organize course content; requires instructor/designer role and write access.

Instructions

Create a module/folder in the course outline. Requires BB_ALLOW_WRITES=1, confirm:true and an instructor/designer role.

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>",
      "title": "<title>"
    },
    "name": "bb_create_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
titleYes
confirmNo
courseIdYes
parentIdNoROOT (default) or a folder id

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 readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-idempotent profile is covered structurally. The description adds context annotations cannot express: an environment gate (BB_ALLOW_WRITES=1), an explicit confirm:true acknowledgement, and a role requirement. It does not mention what is returned or what happens if the parent folder is missing, but against annotation coverage this is solid.

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 no filler: the action and scope come first, the gating conditions second. Every clause carries information the agent needs before calling.

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 five-parameter mutation with no output schema and sparse schema descriptions, the definition covers the access gate and role but omits success behavior, the default value of kind, and whether parentId must reference an existing folder. Adequate to attempt the call, not fully self-contained.

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 20%, so the description should carry more weight. It does explain the confirm flag's required value and implicitly maps 'module/folder' to the kind enum, but courseId, title, and the ROOT-vs-folder-id semantics of parentId are left entirely to the schema.

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 opens with a specific verb and resource ('Create a module/folder') and scopes it to 'the course outline', which separates it from the other bb_create_* siblings that target announcements, assignments, pages, etc. It stops short of naming any sibling explicitly, so the differentiation is inferred from the resource noun rather than stated.

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 hard preconditions (BB_ALLOW_WRITES=1, confirm:true, instructor/designer role) that tell the agent when the call is permitted, which is real guidance. It does not, however, say when to prefer a module versus a folder, or when to use this versus other outline-mutating tools, leaving the choice to the schema's enum.

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