Skip to main content
Glama

Grant extension or exemption

bb_set_grade_exception
Idempotent

Set per-student deadline extensions or exemptions on a grade column to accommodate individual needs. Requires instructor role, confirm:true, and BB_ALLOW_WRITES=1.

Instructions

Set a per-student exception (deadline extension or exemption) on a 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>",
      "userId": "<userId>"
    },
    "name": "bb_set_grade_exception"
  }
}

Input Schema

NameRequiredDescriptionDefault
exemptNo
userIdYes
confirmNo
dueDateNoNew due date (ISO 8601)
columnIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive, idempotent mutation. The description adds genuinely useful behavioral context beyond that: a feature flag, an explicit confirm gate, and an authorization requirement (instructor role). It stops short of stating what happens to an existing exception or whether values are overwritten, which keeps it out of the top band.

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?

Two tight sentences with the core action front-loaded and prerequisites second; no filler. The prerequisite sentence is dense with three separate requirements but each is load-bearing.

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 6-parameter mutation with no output schema and thin schema descriptions, the definition covers the operational gates (flag, confirm, role) but leaves the parameter mechanics and the resulting effect underspecified. An agent could call it but might guess wrong on exempt/dueDate.

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 only 17% (just dueDate), so the description must carry the load, and it largely does not. It hints at exempt vs. dueDate through 'deadline extension or exemption' and gestures at userId via 'per-student', but courseId, columnId, confirm, and exempt are never explained, and the interaction between 'exempt' and 'dueDate' is left ambiguous.

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 gives a specific verb ('Set'), resource ('per-student exception ... on a column'), and enumerates the two exception types (deadline extension, exemption). The 'per-student' qualifier implicitly distinguishes it from course-wide deadline tools, though no sibling is named explicitly.

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 states the preconditions for a successful call (BB_ALLOW_WRITES=1, confirm:true, instructor role), which is useful context. However, it gives no guidance on when to choose this over alternatives such as a course-wide deadline change, and provides no exclusions or when-not conditions.

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