Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List enrolled UAB courses

campus_list_courses
Read-onlyIdempotent

Lists the authenticated user's enrolled subjects for a chosen year or all configured years; non-subject spaces are hidden unless includeNonSubjects is true.

Instructions

List the authenticated user's enrolled subjects for one year, or for every configured year. Non-subject spaces (degree coordination, student council, university info) are hidden unless includeNonSubjects is true; every item carries its category and kind.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
includeNonSubjectsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real behavior: non-subject spaces are filtered out by default and only surfaced via includeNonSubjects, and each returned item carries category and kind. It does not mention pagination, ordering, or cost of fetching every year, which keeps it below 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?

Two tight sentences, front-loaded with the core action, then the filtering rule. The trailing clause about category and kind is mild return-shape detail but still earns its place given there is no output schema.

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?

For a two-parameter, no-output-schema listing tool, the description covers scope, default filtering, and per-item shape well enough to call it correctly. The main residual gap is the year string format and the absence of any note on result size when iterating all years.

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 is 0%, so the description must carry the load, and it does explain both parameters' meaning (year selects one year vs all; includeNonSubjects toggles the hidden non-subject spaces). However, the required 'YYYY-NN' academic-year format and what happens with an unconfigured year are left unstated.

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?

States a specific verb and resource: 'List the authenticated user's enrolled subjects', with the scope qualifier 'for one year, or for every configured year'. It is clearly distinct from search-style siblings like campus_find_courses by emphasizing enrolled subjects, though it never names an alternative explicitly.

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?

Usage is only implied: omit year to get all configured years, pass year for one. There is no statement of when to prefer this over campus_find_courses or campus_list_years, and no prerequisites or exclusions beyond the includeNonSubjects note.

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