Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB course quizzes

campus_list_quizzes
Read-onlyIdempotent

Retrieve quiz availability, limits, grading rules, and attempt settings for a specific course to review assessment configuration before planning or taking quizzes.

Instructions

Read quiz availability, limits, grading rules, and attempt settings for one course.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description does add genuine value by saying what data comes back (availability, limits, grading rules, attempt settings) rather than just 'lists quizzes'. It says nothing about pagination, empty results, or whether the caller must be enrolled in the course.

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?

One sentence, no filler, and the resource and scope are front-loaded. It is efficient, though the same token budget could have carried one clause about the year parameter instead of a longer list of quiz attributes.

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?

There is no output schema, so the description reasonably explains the shape of the returned settings, and the annotations cover safety. However, with zero schema description coverage on two required parameters and no guidance on how this differs from neighbouring course-scoped tools, an agent still lacks the details needed to call it confidently.

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

Parameters2/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 full burden for both parameters, and it does not meet it. 'For one course' loosely maps to courseId, but it never explains that year is a period string matching ^\d{4}-\d{2}$ (an academic year such as 2024-25) nor what happens if an invalid or non-enrolled year is supplied. This is a meaningful gap for a two-required-parameter tool.

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 a specific resource (quizzes) and a specific scope ('for one course'), and it enumerates what is read: availability, limits, grading rules, attempt settings. That is enough for an agent to separate it from campus_list_assignments or campus_get_grades. It stops short of naming a sibling explicitly or stating what the tool does not cover (e.g., quiz questions or submissions).

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?

There is no when-to-use guidance: no statement of prerequisites, no mention of a related tool for quiz attempts or results, and no condition under which an agent should prefer this over the other course-scoped list tools. The only implicit cue is 'for one course', which the required courseId already implies. An agent must guess when this is the right call.

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