Skip to main content
Glama
Sign In
nyu-brightspace-mcp

nyu-brightspace-mcp

by xyspg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_grades

Read-only

Retrieve released assignment grades with points, weight, comments, and final grade. Filter by course or get all current-semester grades.

Instructions

My released grades per item (points, weight, comments) and the final grade if released.

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

Input Schema

NameRequiredDescriptionDefault
courseNoCourse filter. Omit for all current-semester courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as read-only, and the description adds useful behavior: only released items are returned, and the final grade appears only if it is released. It also names the included fields (points, weight, comments), giving the agent a clear expectation of response content without contradicting annotations.

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?

One compact sentence communicates scope, return content and a conditional ('if released'), with no filler. It front-loads the subject and avoids repeating annotations or schema details.

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 simple read-only tool with one optional parameter, the description names what is returned (points, weight, comments) and the conditional final grade. The schema supplies the remaining default behavior (omit course → current semester), so nothing needed for correct invocation 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 coverage for the single `course` parameter is 100%, with a clear description ('Course filter. Omit for all current-semester courses.'). The tool description adds no additional semantics about the parameter, 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 clearly identifies the resource ('grades') and the return payload ('points, weight, comments', plus final grade if released), and the qualifier 'released' distinguishes it from assignment listings like get_assignments. It is not a 5 because 'per item' does not spell out which grade-item types are covered.

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 phrasing 'My released grades' implies the primary use case—viewing the caller's own visible grades—and the optional course filter is documented in the schema. However, the description never states when to use this over siblings such as get_assignments or get_quizzes, nor any exclusion criteria.

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

Deploy Server

Other Tools