Skip to main content
Glama

Change assignment deadline

bb_set_assignment_deadline
Idempotent

Update an assignment due date on its Blackboard gradebook column, requiring instructor role, confirm flag, and write access enabled.

Instructions

Update an assignment due date on its gradebook column. 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>",
      "columnId": "<columnId>",
      "dueDate": "<dueDate>"
    },
    "name": "bb_set_assignment_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
dueDateYesISO 8601 timestamp
columnIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation/idempotency profile is covered. The description adds context beyond that: the write-flag gate, the confirm:true requirement, and the instructor role prerequisite, which are exactly the operational constraints an agent needs before attempting a write. It does not explain failure behavior when the write flag is off or what confirm does if omitted.

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 its target are front-loaded, followed by the gating requirements, which is the right ordering for an agent deciding whether it can call the tool at all.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with no output schema, the definition covers the essentials: what changes, which column is targeted, and the environment/permission gates. It lacks notes on side effects such as existing student deadline exceptions or what the response contains, but nothing critical to invoking it correctly is missing.

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?

With schema coverage at only 25%, the schema documents just dueDate as ISO 8601; columnId and courseId have no descriptions in either place. The description partially compensates by tying confirm to a required value of true, but the two identifier parameters remain semantically undocumented beyond their names, so it does not fully close the coverage gap.

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 ('Update an assignment due date') and locates it precisely ('on its gradebook column'), which separates it from create/get assignment siblings. It stops short of naming an adjacent tool such as bb_set_grade_exception, so it is clear but not sibling-differentiating at the top level.

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?

It gives the conditions required to call the tool (BB_ALLOW_WRITES=1, confirm:true, instructor role) but frames these as prerequisites rather than when-to-use versus alternative guidance. There is no statement of when a caller should use this instead of a grade-exception or assignment-creation tool, leaving usage implied.

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