Skip to main content
Glama
D2L BrightSpace MCP

D2L BrightSpace MCP

Get Classlist Emails

get_classlist_emails
Read-only

Fetch every email address for instructors, TAs, and students in a specified course, so you can email the whole class or gather enrolled contact info. Returns emails only.

Instructions

Fetch all email addresses for everyone in a course: instructors, TAs, and students. Use this when the user wants a list of emails for a class, needs to email the whole class, or wants contact info for everyone enrolled. Returns emails only, with no names or roles. For names, roles or finding a specific instructor or TA, use get_roster instead. Example: "Give me everyone's email in my Biology course."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "courseId": "<courseId>"
    },
    "name": "get_classlist_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYesCourse ID to get emails for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/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 genuinely useful return-scope context ('Returns emails only, with no names or roles'), which sets expectations beyond the annotations. It stops short of deeper traits like auth requirements or pagination, keeping it at 4.

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?

Four tight sentences, front-loaded with the verb and scope, followed by use cases, the sibling redirect, and a short example. Every sentence earns its place with no redundancy.

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?

For a one-parameter read tool with no output schema, the description covers purpose, use cases, the key alternative, and what is returned (emails only, no names/roles). Nothing an agent needs to call it correctly is missing.

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 single courseId parameter is already fully documented by the schema. The description adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 all email addresses for everyone in a course') and enumerates the covered roles, then explicitly distinguishes itself from the sibling get_roster. An agent can tell exactly what it does versus get_roster without opening a 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?

Names concrete use cases ('needs to email the whole class', 'wants contact info') and explicitly routes the alternative: 'For names, roles or finding a specific instructor or TA, use get_roster instead.' This is exactly the when/when-not/alternatives pattern.

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