Skip to main content
Glama

Get course

bb_get_course
Read-only

Retrieve a single Blackboard course by its internal ID to view its name, code, description, term, availability, and enrollment settings.

Instructions

Get one course by its internal id (e.g. _12345_1). Returns name, code, description, term, availability and enrolment settings.

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

Input Schema

NameRequiredDescriptionDefault
courseIdYesInternal course id from bb_list_courses, e.g. _12345_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 safety is covered. The description adds real value beyond them by enumerating what the response contains (name, code, description, term, availability, enrolment settings), which matters since no output schema exists.

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 tight sentences, zero filler: the first establishes the operation and key format, the second lists return fields. The most decision-relevant information (what it returns, how to identify the course) is front-loaded.

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?

For a one-parameter read tool with full annotation coverage and no output schema, the definition supplies the essentials: identification method and returned fields. Only the relationship to sibling course tools is left implicit, a minor gap given the tool's simplicity.

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 courseId parameter is already documented in the schema with the same _12345_1 example. The description repeats rather than extends that meaning, so the baseline 3 applies.

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?

States a specific verb and resource ("Get one course") and pins the retrieval key to an internal id with a concrete example (_12345_1). The phrase "one course" implicitly contrasts with browsing/listing siblings, though it never names bb_browse_course or bb_list_courses 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?

Usage is implied rather than stated: the agent can infer this is for fetching a single known course, and the schema notes the id comes from bb_list_courses. There is no explicit guidance on when to prefer this over bb_browse_course or what to do if the id is unknown.

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