Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB course resources

campus_list_resources
Read-onlyIdempotent

Flatten a course into usable activities, links, and file metadata with section context; filter by module types to narrow large responses.

Instructions

Flatten a course into directly usable activities, links, and file metadata with section context. The response is heavy (often tens of thousands of characters); use moduleTypes to narrow it when only some activity types are needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "courseId": "<courseId>"
    },
    "name": "campus_list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes
moduleTypesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds non-annotation context that matters: the payload is often tens of thousands of characters and should be narrowed via moduleTypes. It still omits auth requirements and whether the flattening spans all sections/materials, so it is not fully transparent.

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 sentences with no filler; the payload shape is front-loaded and the size warning plus filtering advice follow immediately. "Flatten" and "directly usable" are slightly jargon-y but earn their place as shorthand for the normalized output.

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?

With no output schema, the description does well to characterize the return as a large flat activity/link/file list. But for a 3-parameter tool with zero schema description coverage, leaving the required year parameter and the semantics of moduleTypes values unexplained is a real gap an agent could hit on first call.

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 description coverage is 0%, so the description carries the burden. It explains moduleTypes' purpose (filter by activity type) and implies courseId via "a course", but the required year parameter (format YYYY-YY per the schema pattern) gets no mention, and moduleTypes' accepted values/enum-like strings are never clarified.

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?

"Flatten a course into directly usable activities, links, and file metadata with section context" names the resource (a course) and what the output contains (activities, links, file metadata, section context), so the agent knows this is an aggregate listing rather than a single-entity fetch. It does not explicitly differentiate itself from siblings such as campus_get_course_contents or campus_get_course_actions, which likely overlap.

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?

It gives one concrete usage hint — pass moduleTypes to narrow when only some activity types are needed — and warns the unfiltered response is heavy. However, it never states when to prefer this over the course-contents/actions siblings, so the choice between overlapping tools is left to inference.

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