Skip to main content
Glama

List my courses

bb_list_courses
Read-only

List every course the signed-in user is enrolled in with internal course ID, display name, code, and role, so the correct IDs can be used by other course-specific tools.

Instructions

List every course the signed-in user is enrolled in, with the internal course id (e.g. _12345_1), display name, course code and role. Course ids from here are required by the other tools.

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 the user has hidden in the Blackboard UI. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/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 value on top by disclosing the return payload, including the exact id format (e.g. _12345_1), and the cross-tool dependency on those ids. It says nothing about pagination or result size limits, which keeps it out of the 5 band.

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 core action and return shape, then the dependency hint. No filler, no restatement of the title, and every clause carries information an agent needs.

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, the description correctly compensates by listing the fields returned and the id format. For a zero-required-parameter read tool with full schema coverage and clear annotations, little else is needed; only the hidden-course behavior is left entirely to the schema.

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 parameter includeHidden is fully documented in the schema with its default. The description never mentions hidden courses, but it does not need to; baseline 3 applies since the schema does all the parameter work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List every course the signed-in user is enrolled in") and pins the scope to the authenticated user, which separates it from roster/course-browse siblings. It even enumerates the returned fields (internal id, display name, course code, role), so an agent knows exactly what it gets without opening anything else.

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

Usage Guidelines4/5

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

"Course ids from here are required by the other tools" is a strong, actionable usage signal that tells the agent to call this first as a prerequisite. It stops short of explicit when-not guidance (e.g. when to reach for a single-course browse tool instead), so it does not reach the top band.

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