Skip to main content
Glama
Sign In
Blackboard MCP

Blackboard MCP

by Mattlo0546
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bb_announcements

Retrieve recent Blackboard announcements for a specified course or all current courses, optionally limited to a chosen number of days.

Instructions

Recent announcements for one course, or for all current courses if none is given.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
courseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. Beyond the course-omission scoping behavior, it says nothing about read-only nature, auth requirements, or result limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single efficient sentence with the scoping rule front-loaded. No waste, but it is arguably too terse for the schema gaps it must cover.

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 simple two-parameter read tool with no output schema, the description covers the course scope but leaves the days parameter and return shape unaddressed, leaving a real gap an agent must guess at.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It explains the course parameter's null/omitted behavior but says nothing about the days parameter (default 14) or what 'recent' actually bounds.

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 resource (announcements) with clear scope: one course, or all current courses if course is omitted. The listing verb is implied rather than explicit, but an agent can distinguish it from siblings like bb_courses or bb_upcoming.

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?

The phrase 'for all current courses if none is given' implicitly tells the agent that omitting course widens scope, which is useful. However, it names no alternatives (e.g., bb_upcoming) and gives no condition for choosing between them.

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