Skip to main content
Glama

Upload group file

bb_upload_group_file

Uploads a local file to a specified Blackboard course group's file area so group members can access shared resources. Requires write access and explicit confirmation.

Instructions

Upload a file to a group file area. Requires BB_ALLOW_WRITES=1 and confirm:true. Experimental: depends on the group tool being enabled.

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>",
      "groupId": "<groupId>",
      "filePath": "<filePath>"
    },
    "name": "bb_upload_group_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
groupIdYes
courseIdYes
filePathYesAbsolute local path

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 already declare readOnlyHint=false and destructiveHint=false, but the description adds genuinely new context: a server-side write gate (BB_ALLOW_WRITES=1), the requirement to pass confirm:true, and an experimental dependency on the group tool. The remaining gap is that it does not say what happens to an existing file of the same name on re-upload, which matters for a non-idempotent operation.

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?

Three short sentences, front-loaded with the action, then the gating conditions, then the caveat. Every sentence carries information, with only minor redundancy between the title and the first sentence.

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 only 25% schema coverage, the description covers the critical gating and experimental status but omits overwrite/duplicate behavior and any hint of what a successful call returns. Adequate to avoid immediate failure, not complete enough to call confidently.

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 25% — just filePath ('Absolute local path') is documented. The description partially compensates by explaining that confirm must be true, which the schema leaves as a bare boolean. But courseId and groupId receive no meaning beyond their names, so the low-coverage gap is only partly filled.

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: 'Upload a file to a group file area.' That is clearly distinct from siblings such as bb_get_group or bb_attach_rubric. It does not explicitly contrast itself with any named alternative, but the action and target are unambiguous.

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 prerequisites (BB_ALLOW_WRITES=1, confirm:true) that effectively say when the call will succeed, which is useful implied usage guidance. However, it never says when to prefer this tool over alternatives or what conditions should stop an agent from calling it, so guidance is only partial.

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