Skip to main content
Glama
Sign In
blackboard-mcp

blackboard-mcp

by felipedias-ie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Blackboard terms

bb_list_terms
Read-only

Lists academic terms and their date ranges, providing a clear view of available terms for scheduling or reporting.

Instructions

Lists academic terms defined on the instance, with their date ranges.

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
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description carries a lighter burden. It adds that results include date ranges, which is helpful, but it does not disclose ordering, pagination behavior, or what happens when limit is omitted. This is adequate given the annotation coverage.

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, direct sentence that says what the tool does and what it returns. No wasted words or repetition of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the description omits the meaning of the optional 'limit' parameter and does not describe the default return format or pagination. With no output schema and no parameter descriptions anywhere, an agent lacks enough information to fully understand all call options.

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

Parameters1/5

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

Schema description coverage is 0% for the single 'limit' parameter, and the tool description does not mention it at all. With no support from the schema description, the tool description leaves the parameter's meaning entirely to inference, so it fails to compensate.

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 ('lists'), resource ('academic terms'), scope ('defined on the instance'), and output detail ('with their date ranges'). Clearly differentiates from sibling list tools such as bb_list_courses and bb_list_conversations.

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 the name and description: it is the read-only listing for academic terms. However, it does not explicitly say when to use this versus other list tools, mention prerequisites, or note how the limit parameter might affect call decisions.

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

Deploy Server

Other Tools