Skip to main content
Glama

List assignments

bb_list_assignments
Read-only

List course assignments and graded activities with due dates, points, allowed attempts, and submission status; locate them by course ID, code, or unique name fragment.

Instructions

List assignments and graded activities in a course with due dates, points, allowed attempts, and whether the student has submitted. Accepts a course id, course code (e.g. COURSE101_12345_Fall_2026) or unique name fragment.

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_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, default 50
offsetNo
courseIdYesCourse id, course code, or unique name fragment
includeSubmittedNoInclude already-submitted items (default true)
includeInstructionsNoInclude instruction text (default false; use bb_get_assignment for details)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 value by disclosing the fields returned (due dates, points, attempts, submitted flag), but it never mentions that already-submitted items are included by default or how pagination behaves, both of which affect the result set.

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, front-loaded with the resource and its returned fields, then the identifier formats. Every clause carries information an agent needs; there is no filler or repetition of the tool name.

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, describing the returned attributes is exactly the right compensation, and it is done here. The remaining gap is behavioral rather than semantic: default filtering of submitted items and pagination semantics are left to the schema's parameter descriptions, which is acceptable but not fully self-contained.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3; the description earns a point by giving a concrete course-code format example (COURSE101_12345_Fall_2026) that the schema's terse 'Course id, course code, or unique name fragment' does not supply. The limit/offset/includeSubmitted/includeInstructions parameters are left entirely to the schema.

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 states a specific verb and resource ('List assignments and graded activities in a course') and enumerates the returned attributes (due dates, points, allowed attempts, submission status). It does not differentiate itself from sibling listing tools such as bb_list_assessments or bb_list_content, so an agent must infer the boundary from the names alone.

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 'in a course' plus the accepted course identifier, which tells the agent this is the per-course assignment listing. There is no explicit when-to-use/when-not guidance, no mention of alternatives such as bb_list_assessments or bb_get_assignment, and no stated prerequisites.

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