Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get personal UAB H5P attempts

campus_get_h5p_attempts
Read-onlyIdempotent

Retrieve attempt summaries for one H5P activity from the authenticated user's account by supplying the academic year and activity ID.

Instructions

Read the authenticated user's attempt summaries for one H5P activity.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
h5pActivityIdYes

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, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds genuine value by saying results are the authenticated user's own, implying no access to other learners' attempts, but it says nothing about return volume, pagination, or what happens when the year or activity has no attempts.

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 front-loaded sentence with no filler, and the two scoping constraints (authenticated user, one activity) appear immediately. It is efficient, but the same brevity is what leaves the year parameter unexplained.

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 would ideally characterize what an "attempt summary" contains, and both parameters are undocumented in the schema. Given the tool is a simple read with only two required fields, the one-sentence definition is workable but under-informative for an agent that must construct a valid year value.

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, yet it only loosely hints at h5pActivityId via "one H5P activity". The required year parameter is never mentioned, and its expected semantics (academic year versus calendar year, and the YYYY-MM period format) are left entirely to the JSON pattern.

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 states a specific verb ("Read") and resource ("attempt summaries") and scopes them precisely to the authenticated user and a single H5P activity, which distinguishes it from an aggregate results tool. It stops short of naming any sibling such as campus_get_h5p_results, so the differentiation must be inferred from the wording alone.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named even though campus_get_h5p_results and campus_list_h5p_activities sit right next to it. The phrase "one H5P activity" implies the tool is per-activity rather than course-wide, but the agent must guess the rest.

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