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

nyu-brightspace-mcp

by xyspg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

login

Open a Chrome window for NYU NetID and Duo authentication, re-establishing Brightspace access when tools report an unauthenticated session.

Instructions

Open a Chrome window for NYU NetID + Duo login. Use when other tools report the session is not logged in. The user must complete Duo on their phone. Waits up to ~100s; if still pending, tell the user to finish and call auth_status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Discloses key behavioral traits beyond the annotations: it opens a Chrome window, requires the user to complete Duo on their phone, waits up to ~100s, and has a defined fallback when pending. This goes well beyond readOnlyHint=false and openWorldHint=true.

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?

Three sentences with no filler. The main action is front-loaded, followed by the trigger condition, user dependency, timeout, and next-step guidance.

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 zero-parameter interactive login tool, the description covers the full workflow: when to call it, what happens, what the user must do, how long it waits, and what to do on timeout. The reference to auth_status closes the loop with an existing sibling tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the input schema is fully covered, so the baseline of 4 applies. There are no parameter semantics for the description to add.

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: open a Chrome window for NYU NetID + Duo login. It is clearly distinguishable from the sibling auth_status, which is a status-checking tool.

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 says to use it when other tools report the session is not logged in. It also gives follow-up instructions to tell the user and call auth_status if login is still pending, so the agent knows exactly when and how to proceed.

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