Skip to main content
Glama

List assessments

bb_list_assessments
Read-only

Lists graded assignments and tests in a Blackboard course, including type, due date, points, attempts, and visibility.

Instructions

List graded assessments (assignments, tests) in a course with type, due date, points, attempts and visibility.

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

Input Schema

NameRequiredDescriptionDefault
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are restricted to graded items and the payload includes type, due date, points, attempts, and visibility. It omits ordering, pagination, and what happens for courses with no assessments.

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?

One dense sentence that front-loads the action and resource, followed by the returned attribute list. Nothing is wasted, though the trailing attribute list reads as a run-on rather than structured information.

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?

With no output schema, enumerating the returned fields is the right compensating move, and with a single required parameter the tool is simple enough that little more is needed. Pagination and result ordering are the only material gaps for a list operation.

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?

There is a single parameter, courseId, at 0% schema description coverage, but the description's phrase 'in a course' conveys its meaning indirectly. No format, ID source, or validation behavior is added beyond the obvious string identifier.

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 and resource ("List graded assessments") and parenthetically defines the domain as assignments and tests, which helps separate it from bb_list_assignments. It stops short of explicitly contrasting itself with that sibling, so an agent must still infer the boundary.

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?

Usage is implied by scope ('in a course') and by the qualifier 'graded', which hints this is for grade-bearing items rather than all course content. There is no explicit when-to-use vs. when-not guidance and no named alternative such as bb_list_assignments or bb_get_assessment.

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