Skip to main content
Glama

Grade a submission

bb_grade_submission
Idempotent

Enter or change one student's grade and feedback on a Blackboard column, requiring confirmation and grading-role access.

Instructions

Enter or change a grade and feedback for one student on a column. Requires BB_ALLOW_WRITES=1, confirm:true and a grading 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>",
      "userId": "<userId>"
    },
    "name": "bb_grade_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreNo
exemptNo
userIdYes
confirmNo
columnIdYes
courseIdYes
feedbackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, so the safety profile is covered. The description adds genuinely useful context beyond that: an environment write gate, a confirm flag requirement, and an authorization role requirement — all of which materially affect whether the call should be attempted. It stops short of saying whether an existing grade is overwritten or what happens to submissions without one, but the added gating detail is substantive.

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?

A single sentence, front-loaded with the action and scope, then immediately the preconditions. Every clause carries information; there is no filler or repetition of the title.

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 mutation tool with no output schema and zero schema description coverage across seven parameters, the description covers the highest-risk elements (write gate, confirmation, role) well. It is still thin on the semantics an agent needs to call it correctly — what 'exempt' does, the score's unit and range, and whether existing grades are replaced. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It only implicitly covers score, feedback and confirm (via 'confirm:true'); the 'exempt' parameter is never mentioned despite being a non-obvious grading concept, and there is no indication of the score scale (points vs. percentage) or valid range. Three required ID parameters are obvious by name, but the domain-specific ones are left undocumented.

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 names a specific verb pair (enter/change) and a precise resource scope: one grade plus feedback, for one student, on one column. That is far more than a restatement of the title. It does not, however, distinguish itself from related siblings such as bb_set_grade_exception, leaving the boundary between grading and grade-exception handling implicit.

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 concrete preconditions for use (BB_ALLOW_WRITES=1, confirm:true, a grading role), which tells the agent when the call will succeed but not when to prefer it over an alternative. No when-not-to-use guidance or named alternative is provided. Usage is implied by the prerequisites rather than framed as a decision rule.

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