Skip to main content
Glama
D2L BrightSpace MCP

D2L BrightSpace MCP

Get My Grades

get_my_grades
Read-only

Fetch your D2L Brightspace grade breakdown for a specific course or all enrolled courses, including grade items, points, percentages, and comments to check scores, marks, and class performance.

Instructions

Fetch your grade breakdown for a specific course or all enrolled courses in D2L Brightspace. Shows grade items (grade columns) with points, percentages, and comments. Pass course with a name or code when you know it, or courseId when you have the ID. Use this when the user asks about grades, grade items, grade item, scores, marks, GPA, academic performance, or how they're doing in a class in Brightspace or D2L. Example: "What's my current grade in Calculus?"

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

Input Schema

NameRequiredDescriptionDefault
courseNoCourse name or code to get grades for, for example "CS 101". Use this instead of courseId when you know the name.
courseIdNoCourse ID to get grades for. If omitted, returns grades for all enrolled courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.8
    • addedInput schema / properties / course
      Added value: +{
      +  "description": "Course name or code to get grades for, for example \"CS 101\". Use this instead of courseId when you know the name.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A3.9/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 real behavioral value on top: it says an omitted course scope returns all enrolled courses, and it discloses the shape of the payload (points, percentages, comments). It does not mention any auth/permission requirements or freshness of grade data, which keeps it short of a 5.

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?

The structure is good: purpose first, then what's returned, then parameter routing, then trigger phrases and an example. It loses a point for keyword stuffing ('grade items, grade item, scores, marks, GPA, academic performance') and for repeating 'Brightspace or D2L' when D2L Brightspace was already named in the first sentence.

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?

There is no output schema, so the description must describe the return, and it does so adequately (grade items with points, percentages, comments) along with the default all-courses scope. For a simple two-parameter read tool with readOnly annotations, that's nearly everything an agent needs; only the absence of any guidance on the get_grade_outlook alternative leaves a gap.

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 both parameters are already documented in the schema, including the 'use this instead of courseId' and 'if omitted, returns all enrolled courses' notes. The description's 'Pass course with a name or code when you know it, or courseId when you have the ID' largely restates the schema rather than adding new semantics, 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?

The description opens with a specific verb and resource: 'Fetch your grade breakdown for a specific course or all enrolled courses in D2L Brightspace,' and clarifies what a result contains ('grade items (grade columns) with points, percentages, and comments'). It is clearly distinct from most siblings, but it never distinguishes itself from the closely related get_grade_outlook sibling, which an agent could easily confuse with this one.

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?

It gives strong positive triggers ('grades, grade items, scores, marks, GPA, academic performance, how they're doing in a class') plus a concrete example, which is solid when-to-use guidance. It also routes between parameters ('Pass course with a name or code when you know it, or courseId when you have the ID'). What's missing is any when-not guidance or explicit routing to get_grade_outlook for projected/what-if grades.

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