Skip to main content
Glama
D2L BrightSpace MCP

D2L BrightSpace MCP

Get My Courses

get_my_courses
Read-only

Retrieve your enrolled Brightspace courses with names, codes, and IDs, optionally filtering to active courses. Use it to answer questions about current classes or to get a course ID for other queries.

Instructions

Fetch your enrolled Brightspace courses with names, codes, and IDs. Use this when the user asks about their courses, enrolled classes, what they're taking this semester, or needs a course ID for other queries. Example: "What courses am I taking this term?"

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

Input Schema

NameRequiredDescriptionDefault
activeOnlyNoOnly return currently active courses. Defaults to the server's configured activeOnly setting (true unless overridden).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value by disclosing the return shape (names, codes, IDs) and its role as an ID source for other calls, though it says nothing about the activeOnly defaulting behavior or result volume.

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 the verb, resource, and return fields, then follows with usage guidance and an example. Slight redundancy between the 'what they're taking this semester' phrase and the example question, but nothing is wasted.

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 usefully names the fields returned and the tool's role as a course-ID source. For a zero-required-parameter read tool this is nearly complete; only the default activeOnly behavior is left entirely to the schema.

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% and the single activeOnly parameter is fully documented there, so the baseline of 3 applies. The description never mentions filtering by active status, but the schema carries that burden adequately.

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 resource ('Fetch your enrolled Brightspace courses') and enumerates the returned fields (names, codes, IDs). An agent can distinguish it from siblings like get_course_content or get_my_grades 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 Guidelines5/5

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

Explicitly names the triggering user intents ('asks about their courses, enrolled classes, what they're taking this semester') and gives a concrete query example. It also states a downstream use case — obtaining a course ID for other queries — which is exactly the routing information an agent needs.

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