Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get personal UAB H5P results

campus_get_h5p_results
Read-onlyIdempotent

Retrieve H5P attempt report data by selected attempt IDs or all attempts for the authenticated user, using year and activity ID to target results.

Instructions

Read report data for selected H5P attempt IDs, or all attempts belonging to the authenticated user.

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>",
      "h5pActivityId": "<h5pActivityId>"
    },
    "name": "campus_get_h5p_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
attemptIdsNo
h5pActivityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's main added value is the personal scope ('authenticated user'), which hints at an auth requirement. It says nothing about the 100-item cap on attemptIds, ordering, or pagination/truncation of results.

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?

A single tight sentence with the scope decision front-loaded and no filler. It is efficient, though the terseness is partly what leaves required-parameter semantics unexplained.

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?

A report-reading tool with 3 parameters at 0% schema coverage and no output schema needs more than one sentence. The required year filter, the behavior when attemptIds exceeds 100, and the distinction from the sibling attempts tool are all unaddressed.

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 must carry parameter meaning. It does explain attemptIds semantics (empty means all attempts for the user), but the required 'year' parameter (pattern YYYY-MM) is never mentioned, nor is the maxItems=100 limit, leaving two of three parameters undocumented anywhere.

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 ('Read report data ... H5P attempt IDs') and clarifies scope: either the listed attempt IDs or all attempts of the authenticated user. It does not distinguish itself from the sibling campus_get_h5p_attempts, so an agent cannot tell from this text which of the two to call when it just wants attempt listings.

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 'selected attempt IDs, or all attempts belonging to the authenticated user' phrasing implies the two calling modes (pass IDs vs. leave empty), which is real implied guidance. There is no explicit when-not guidance and no named alternative for the adjacent attempts/activities tools.

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