Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get personal UAB quiz attempts

campus_get_quiz_attempts
Read-onlyIdempotent

Read a user's quiz attempt history for one quiz without starting or changing an attempt; optionally filter results by finished, unfinished, or all statuses.

Instructions

Read the authenticated user's attempt history for one quiz without starting or changing an attempt.

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>",
      "quizId": "<quizId>"
    },
    "name": "campus_get_quiz_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
quizIdYes
statusNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description reinforces this with 'without starting or changing an attempt' and adds that results are scoped to the authenticated user, but it says nothing about ordering, limits, or what an attempt record contains.

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?

A single tightly written sentence with the read scope front-loaded and no redundant restatement of the title. Nothing could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three undocumented parameters, an enum filter, and no output schema, the description is too thin. It omits parameter formats, filter behavior, and any sense of return shape, leaving the agent to guess at invocation details.

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 three parameters, and it mentions none of them. It never explains that 'year' expects a YYYY-MM string, that 'quizId' targets a specific quiz, or that 'status' filters by finished/unfinished.

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 gives a specific verb (read) and resource (attempt history for one quiz) and scopes it to the authenticated user. It distinguishes itself in substance from grade-oriented siblings like campus_get_quiz_best_grade, though it does not name 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?

The clause 'without starting or changing an attempt' implies this is the read-only inspection path rather than an attempt-creating one, which gives some usage framing. However, there is no explicit guidance on when to choose this over campus_get_quiz_best_grade or other quiz tools, and no prerequisites are stated.

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