Skip to main content
Glama

List terms

bb_list_terms
Read-only

Lists academic terms configured on the Blackboard instance so you can identify available term IDs and filter courses or content by term.

Instructions

List academic terms configured on the Blackboard instance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 structurally. The description adds only that terms are instance-level configuration; it says nothing about ordering, pagination, whether all terms or only active ones are returned, or permission requirements. Beyond the annotations, the added behavioral context is thin.

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?

A single sentence with no filler, and the resource is front-loaded immediately after the verb. Nothing in it is redundant or restates the title wastefully.

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?

For a zero-parameter read-only list, the definition is serviceable but there is no output schema, so the shape of a returned term (ID, name, dates, status) is undocumented anywhere. An agent knows it can fetch terms but not what it will receive or how to use the result downstream.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No argument filtering or scoping options exist that would need explanation.

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: "List academic terms" is concrete and distinguishable from sibling list tools such as bb_list_courses or bb_list_announcements. The qualifier "configured on the Blackboard instance" adds scope. It stops short of explicitly contrasting with any sibling, but the resource noun does most of the disambiguating work.

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 guidance on when to use this tool, what question it answers (e.g., discovering term IDs for later course filtering), or any prerequisite or exclusion. An agent must infer usage purely from the name and the word "terms".

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