Skip to main content
Glama

Attach rubric to assessment

bb_attach_rubric
Idempotent

Associate a rubric with a Blackboard gradebook column for instructor-managed grading. Use it to link rubric criteria to an existing column; requires write access and confirmation.

Instructions

Associate a rubric with a 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>",
      "rubricId": "<rubricId>"
    },
    "name": "bb_attach_rubric"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
columnIdYes
courseIdYes
rubricIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 write/idempotency profile is covered structurally. The description adds genuine context beyond that – the environment flag gate, the confirm token, and the instructor-role requirement. However, it omits a key behavior: whether attaching a rubric replaces or coexists with one already on the column.

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 sentences, zero filler, with the action front-loaded and the gating requirements immediately after. Nothing is redundant.

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 three-required-parameter mutation with no output schema, the description supplies the essential gating conditions an agent needs to avoid a failed call. The remaining gap is the replace-versus-add question, which matters but is a narrower concern than the prerequisites it already states.

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 0% for four parameters, so the description must carry the meaning. It does explain 'rubric' and 'gradebook column' (covering rubricId and columnId) and clarifies confirm as a boolean acknowledgement, but courseId and the string-identifier format of each ID are left entirely to inference.

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 uses a specific verb ('Associate') and names both resources precisely: a rubric and a gradebook column. It is unambiguous what the tool does, though it does not explicitly distinguish itself from any sibling tool or state the inverse case.

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 hard prerequisites for use (BB_ALLOW_WRITES=1, confirm:true, instructor role), which is real guidance about the conditions under which invocation succeeds. It stops short of saying when to choose this over alternatives or what to do if a rubric is already attached.

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