Skip to main content
Glama

List my Blackboard courses

bb_list_courses
Read-onlyIdempotent

Retrieve the Blackboard courses you are enrolled in, ordered by most recent access, and optionally include unavailable or hidden courses to review your current course list.

Instructions

Courses you are enrolled in, most recently accessed first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bb_list_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeHiddenNoInclude courses that are not currently available

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's genuine addition is the ordering guarantee ('most recently accessed first'), which annotations cannot express. It does not disclose that unavailable courses are omitted by default, which is the one behavioral fact an agent most needs here.

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?

One short sentence with zero filler, and the resource identity is front-loaded ahead of the ordering detail. Nothing is redundant with the title or schema.

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?

This is a simple, parameterless-by-default read with no output schema, so the bar is low, but the description omits the default hidden-course behaviour and any indication of what a course record contains. Adequate to select the tool, thin for invoking it deliberately with includeHidden.

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 100%, and the single optional parameter includeHidden is documented in the schema as 'Include courses that are not currently available'. The description adds nothing about it, so the baseline 3 applies; it neither compensates for nor undermines 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 names the resource precisely ('Courses you are enrolled in'), which combined with the title makes the listing action unambiguous. It also states the sort order. It stops short of distinguishing itself from the closest sibling, bb_course_contents, which an agent must infer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement of the default hidden-course exclusion, no pointer to bb_course_contents for per-course detail, and no prerequisites. The agent must infer usage purely from the resource name.

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