Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB H5P activities

campus_list_h5p_activities
Read-onlyIdempotent

Retrieve H5P activity metadata, grading settings, and tracking configuration for one course to review how activities are configured and tracked.

Instructions

Read H5P activity metadata, grading settings, and tracking configuration 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_h5p_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.9/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 covered. The description adds useful content about what the read returns (metadata, grading settings, tracking configuration) and that it is scoped per course, but says nothing about pagination, volume, or what happens if no activities exist.

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 or redundancy. Its brevity borders on under-specification rather than waste, but structurally it is clean and easy to parse.

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?

With 0% schema description coverage and no output schema, the description should explain the year parameter and roughly what fields come back; it does neither. For a two-required-parameter, open-world read against a course, this leaves material gaps for correct invocation.

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 and largely fails: 'one course' loosely maps to courseId, but the required 'year' parameter (pattern ^\d{4}-\d{2}$) is never mentioned, leaving the agent to infer an academic-year format with no help. Only one of two required parameters gets even indirect coverage.

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 ('Read') and resource ('H5P activity metadata, grading settings, and tracking configuration') scoped to 'one course', which is concrete enough to act on. It does not distinguish this tool from siblings such as campus_get_h5p_attempts or campus_get_h5p_results, and the mismatch between the tool name ('list ... activities') and the singular 'Read ... for one course' framing leaves the cardinality slightly ambiguous.

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 guidance on when to choose this over the H5P attempts/results siblings or the SCORM activities list, and no prerequisite chain is named (e.g., resolving year and courseId first). 'For one course' implies scoping but gives no exclusion or alternative routing.

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