Skip to main content
Glama
D2L BrightSpace MCP

D2L BrightSpace MCP

Export Due Dates To Calendar

export_due_dates_calendar
Idempotent

Build an iCalendar file of upcoming Brightspace assignments and quizzes with links back to each item and a one-day reminder, so due dates can be added to Google Calendar, Apple Calendar, or Outlook.

Instructions

Builds an iCalendar (.ics) file of upcoming assignments and quizzes that opens in Google Calendar, Apple Calendar and Outlook. Each event has a link back to Brightspace and a one day reminder. By default only unfinished work is included. Pass downloadPath (an absolute folder) to save the file, otherwise the calendar text is returned. Example: "Put my upcoming due dates in Google Calendar."

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": "export_due_dates_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdNoOnly include this course
daysAheadNoHow many days ahead to include
downloadPathNoAbsolute path to a directory. When given, the .ics file is saved there instead of returned as text.
includeSubmittedNoAlso include work that is already submitted or graded. Default is only work still left to do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the write-ish nature is flagged; the description adds the practical consequence — a file is written only when downloadPath is supplied, otherwise text is returned — plus event contents (Brightspace backlink, one-day reminder) and the default filtering rule. It omits edge behavior such as overwriting an existing file at that path.

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?

Front-loads what is produced, then scoping defaults, then the downloadPath branch, closing with a natural-language example. Every sentence carries information, though the multi-client app listing is slightly decorative.

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

Completeness5/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 still covers the two return modes (raw calendar text vs saved .ics), what each event contains, and the default filter, which is everything an agent needs before invoking a zero-required-parameter export tool.

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 the baseline is 3. The description elaborates on downloadPath ('an absolute folder' plus fallback to text) and on the includeSubmitted default, but adds nothing about courseId or daysAhead beyond what the schema already states.

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 and artifact: builds an iCalendar (.ics) file of upcoming assignments and quizzes. The output format (a file importable into Google/Apple/Outlook) clearly separates it from read-only siblings like get_upcoming_due_dates or get_calendar_events, so an agent can pick it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: default behavior excludes submitted/graded work, and passing downloadPath switches from returning text to saving a file, reinforced by an example user utterance. It never explicitly excludes alternatives (e.g. 'use get_upcoming_due_dates if you just want a list'), so it falls short of a 5.

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