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

nyu-brightspace-mcp

by xyspg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_quizzes

Read-only

Retrieve Brightspace quiz details including open, due, and close times, time limits, and attempt counts. Filter by course to view quizzes for current semester.

Instructions

Brightspace quizzes/exams with open/due/close times, time limits and attempts.

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

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

B3.2/5.0
Behavior3/5

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

The annotations provide readOnlyHint and openWorldHint, so the description need not restate safety. It adds some output context by enumerating fields, but it does not disclose default scoping (current-semester), pagination, or response structure, leaving meaningful behavioral gaps.

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 description is a single efficient sentence with no filler and the resource is front-loaded. It could be improved by starting with an active verb, but it's appropriately compact for the information provided.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter getter with annotations and no output schema, the description is adequate but sparse. It does not clarify whether the result is a list, mention default course filtering, or elaborate on the returned items beyond a few fields, leaving modest gaps for an agent to infer.

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?

With 100% schema description coverage for the single 'course' parameter, the baseline is 3. The description adds nothing about parameters beyond what the schema already states, so it neither improves nor harms parameter understanding.

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 names the resource (Brightspace quizzes/exams) and the key attributes returned (open/due/close times, time limits, attempts). This distinguishes it from sibling tools like get_assignments, though it relies on the tool name for the verb and does not explicitly state 'list' or 'retrieve'.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus get_upcoming, get_assignments, or other siblings. The only usage context is the course filter description in the schema, which is not part of the description and does not help choose between similar tools.

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