Skip to main content
Glama
alanwtom

blackboard-mcp

by alanwtom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Blackboard assignments

get_assignments
Read-only

List assignments and assessments with due dates, deduplicated from Blackboard course content, gradebook, and calendar. Filter by course or due-date window; read-only.

Instructions

List assignments and assessments with due dates, combined and deduplicated from Blackboard course content, the gradebook, and the calendar. Optionally scope to one course and/or a due-date window. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idNoBlackboard course id from list_courses. Omit to include all courses.
due_afterNoISO date or date-time. A bare date ("2026-09-30") means the start of that day, Syracuse time.
due_beforeNoISO date or date-time. A bare date ("2026-09-30") includes that whole day, Syracuse time.
include_statusNoAlso resolve submitted/graded status (slower: 1-2 extra Blackboard requests per item). Status is "in_progress" for a started or saved draft that was NOT handed in, and "unknown" when Blackboard does not report an attempt either way — treat unknown as undetermined, never as missing work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / due_after / description
      Previous value: -"ISO date — only items due on/after this instant."New value: +"ISO date or date-time. A bare date (\"2026-09-30\") means the start of that day, Syracuse time."
    • changedInput schema / properties / due_before / description
      Previous value: -"ISO date — only items due on/before this instant."New value: +"ISO date or date-time. A bare date (\"2026-09-30\") includes that whole day, Syracuse time."
    • changedInput schema / properties / include_status / description
      Previous value: -"Also resolve submitted/graded status (slower: one extra Blackboard request per item)."New value: +"Also resolve submitted/graded status (slower: 1-2 extra Blackboard requests per item). Status is \"in_progress\" for a started or saved draft that was NOT handed in, and \"unknown\" when Blackboard does not report an attempt either way — treat unknown as undetermined, never as missing work."
  2. 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 and openWorldHint, so the "Read-only" sentence is largely redundant. The description does add genuine behavioral context beyond annotations: the result is merged and deduplicated across three upstream sources, which tells the agent to expect canonicalized output rather than raw per-source records.

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?

Three tight sentences: what it returns and from where, then the optional scoping, then the safety profile. Nothing is repeated and the most distinctive information (deduplication across sources) leads.

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 should ideally hint at the shape of returned items (fields, ordering, status presence), which it does not. Everything needed to invoke the tool correctly is present, though, so the gap is modest.

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%, so all four parameters are already fully documented, including the Syracuse-timezone semantics and the include_status cost/"unknown" caveat. The description only restates course and due-date scoping at a high level, adding no syntax the schema lacks, 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 ("List assignments and assessments with due dates") and adds a distinctive mechanism (combined and deduplicated from course content, gradebook, and calendar) that separates it from get_course_content or get_grades. It stops short of naming the closest siblings, get_upcoming_work and get_assignment_context, so an agent must still infer the boundary.

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?

"Optionally scope to one course and/or a due-date window" implies when the filters matter, but there is no explicit guidance on when to prefer this tool over get_upcoming_work or get_assignment_context, which appear to overlap. Usage is implied rather than stated.

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