Skip to main content
Glama

Submit assignment

bb_submit_assignment
Destructive

Submits an assignment by creating an attempt, uploading files, and posting it for grading; requires write access enabled and confirmation.

Instructions

Submit work to an assignment: creates an attempt, uploads files, and posts it for grading. Requires BB_ALLOW_WRITES=1 and confirm:true. Experimental: verify the attempt in Blackboard after the first use.

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>",
      "contentId": "<contentId>"
    },
    "name": "bb_submit_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText submission body (plain text or HTML)
confirmNo
courseIdYes
contentIdYesAssignment content id from bb_list_assignments
filePathsNoAbsolute local file paths to upload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and non-idempotent, and the description adds real value on top: it discloses the multi-step side effects (attempt creation, file upload, posting for grading), the write-gate environment variable, the required confirm flag, and an experimental-status warning. It does not say what happens on partial failure (e.g., an attempt created but upload failed) or whether a retry spawns a second attempt, which matters for a non-idempotent write.

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?

Three short sentences with no filler, ordered from what it does to what it requires to a caveat. Every clause carries information an agent needs before calling.

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 5-parameter destructive write with no output schema, the definition covers purpose, gating preconditions, and a stability warning, which is close to what an agent needs. The remaining gap is failure/retry semantics on a non-idempotent multi-step operation, which the annotations flag but the description never resolves.

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 coverage is 60%: text, contentId, and filePaths are documented in the schema, and the description usefully supplies the otherwise-bare confirm parameter (confirm:true) and implies the file-upload role of filePaths. However, courseId remains undocumented in both places, and the description adds no detail on the text-vs-file relationship or whether both can be sent.

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 ("Submit work to an assignment") and decomposes it into the three concrete actions it performs: creating an attempt, uploading files, and posting for grading. It does not name or contrast with any sibling (e.g., bb_get_assignment_submission), so an agent must infer the read/write split from the verb alone.

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 preconditions that govern whether the call can succeed (BB_ALLOW_WRITES=1, confirm:true) plus a first-use caution to verify the attempt in Blackboard. It stops short of stating when not to use it or which sibling to call instead, so it is clear context rather than a full when/when-not rule.

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