edhec-mcp

Overview Schema Source Related Servers Discussions Admin

Upcoming deadlines

bb_upcoming

Read-onlyIdempotent

Retrieve upcoming Blackboard course due dates and events for a chosen number of days to track deadlines and plan coursework across all enrolled courses.

Instructions

Calendar items (due dates, events) across all your courses for the next N days.

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

Input Schema

Name	Required	Description	Default
`days`	No	Default 21

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered externally. The description adds the aggregation scope and time-window behavior, but says nothing about result ordering, volume, or what happens at the 120-day maximum, so added value is modest.

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 compact sentence that front-loads the resource and ends with the scope qualifier; nothing is padded. The only weakness is that 'N days' is left abstract when the schema's default of 21 would be worth restating.

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 one-parameter read tool with full annotation coverage and no output schema, this is close to adequate. However, it omits the default window and any indication of result shape or ordering, which would help an agent call it correctly the first time.

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?

With one optional parameter at 100% schema coverage, the schema already documents the bounds and the default of 21. The description only reinforces that the window is forward-looking ('next N days'), which is a marginal but real addition over the schema's bare constraints.

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 concrete resource — calendar items including due dates and events — and a scope, 'across all your courses,' which separates it from course-specific tools like bb_course_contents. It stops short of naming a sibling alternative, so it is clear but not fully disambiguated.

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 'across all your courses' implies this is the aggregated forward-looking view rather than a per-course listing, which weakly guides selection. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as aurion_timetable or bb_announcements, so an agent must infer the routing.

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