Skip to main content
Glama

Create assignment

bb_create_assignment

Creates a graded Blackboard assignment with instructions, due date, points, and attempts, generating both course content and a gradebook column for instructors.

Instructions

Create a graded assignment (content + gradebook column) with instructions, due date, points and attempts. Requires BB_ALLOW_WRITES=1, confirm:true and an instructor 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_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
confirmNo
dueDateNoISO 8601
courseIdYes
parentIdNo
instructionsNo
pointsPossibleNo
attemptsAllowedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false and destructive=false; the description adds meaningful context beyond that — the tool writes to two systems (content plus gradebook column), needs a write-enable flag, an explicit confirm token, and instructor privileges. It does not say whether the operation is reversible or what happens on partial failure, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the action and its dual effect front-loaded, then preconditions. Every clause carries information; no filler. It is slightly over-compressed in the parameter list, which reads as enumeration rather than explanation.

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 non-idempotent mutation tool with 8 parameters and 13% schema coverage, the description covers the what, the dual side effect, and the gating requirements. Gaps remain around parentId's purpose, validation constraints on pointsPossible/attemptsAllowed, and failure behavior. No output schema exists, so return values needn't be explained.

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 13% (just dueDate as ISO 8601), so the description must carry the burden. It names instructions, due date, points and attempts, and effectively explains confirm:true as a required guard, but says nothing about parentId (likely module/section placement), courseId format, or what values attemptsAllowed accepts. Partial compensation for a low-coverage 8-parameter 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?

States a specific verb and resource ('Create a graded assignment') and adds a parenthetical that disambiguates the effect: it writes both content and a gradebook column. That dual effect alone separates it from siblings like bb_create_page or bb_create_announcement. It stops short of naming an alternative outright, so it is clear but not fully sibling-differentiated.

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?

Gives real preconditions an agent must satisfy before calling: BB_ALLOW_WRITES=1, confirm:true, and an instructor role. However, it offers no when-not-to-use guidance and never routes the agent to alternatives such as bb_set_assignment_deadline for changing a due date later or bb_attach_rubric for grading structure. Usage is implied by prerequisites rather than stated as a selection rule.

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