Nexus MCP

Overview Schema Source Related Servers Discussions Admin

list_courses

Read-onlyIdempotent

Fetch a student's Nexus courses with IDs, names, teachers, and terms, filtered by in progress, past, future, hidden, or all status and academic-only enrollment. Use IDs with other tools.

Instructions

List the student's Nexus courses with id, name, short name, teacher and term.

    classification (from Moodle start/end dates): "inprogress" (default), "past",
    "future", "hidden", or "all". academic_only=true drops non-academic enrolments
    (trainings, campus resources) that have no term code. Use `id` with other tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`academic_only`	No
`classification`	No		inprogress

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context: classification is computed from Moodle start/end dates, and non-academic enrolments lack term codes, which explains the filtering semantics.

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?

Front-loads the core purpose, then the classification detail, then the academic_only caveat; every sentence carries information. Slightly awkward formatting with the indented block and quoted default, but no wasted content.

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?

Covers both optional parameters, their defaults, and the id handoff to other tools; with an output schema present it need not spell out return values. A brief note on ordering or whether 'all' includes hidden vs past would make it fully complete.

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?

Schema coverage is 0% and no enums are declared, so the description carries the full burden. It documents all five classification values with the default ('inprogress') and the exact effect of academic_only=true, which is a substantial addition over the bare boolean/string schema.

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 (List) and resource (the student's Nexus courses) and enumerates exactly what each entry contains (id, name, short name, teacher, term). This lets an agent distinguish it from the singular get_course sibling without opening the schema.

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?

Explains when the classification modes apply (derived from Moodle start/end dates, default 'inprogress') and what academic_only=true filters out (trainings, campus resources with no term code), plus the downstream 'use id with other tools' handoff. It stops short of explicitly naming competing siblings like get_course or course_updates.

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