Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB SCORM activities

campus_list_scorm_activities
Read-onlyIdempotent

Read SCORM package metadata, grading rules, attempt limits, and navigation settings for a specific course and academic year.

Instructions

Read SCORM package metadata, grading rules, attempt limits, and navigation 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_scorm_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes the useful detail that the read is scoped to a single course and enumerates what is returned (metadata, grading rules, attempt limits, navigation settings). It says nothing about pagination, error behavior when the course has no SCORM package, or result shape, which is a modest gap for a mutation-free read.

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, tightly worded sentence with the scope ("for one course") and the returned information front-loaded; nothing is wasted. It is perhaps too terse for its responsibilities, but not verbose or poorly structured.

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?

The tool has no output schema, two fully undocumented required parameters, and no usage guidance, so the description carries the full burden and falls short. An agent still cannot determine the year parameter's role, what an "activity" entry looks like, or when to prefer this over campus_get_scorm_structure or campus_list_h5p_activities.

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% for the two required parameters (year as YYYY-MM, courseId as a positive integer). The description only hints at courseId through "for one course" and gives no meaning at all to the year parameter, which is required and has a non-obvious format constraint. With no schema documentation, the description should have compensated and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 enumerates the resource contents (package metadata, grading rules, attempt limits, navigation settings) scoped to "one course." However, it sits in tension with the tool name and title ("List UAB SCORM activities"): the description reads more like fetching configuration/settings than listing activities, so an agent cannot be fully sure whether it returns an activity list. It also offers no differentiation from siblings such as campus_get_scorm_structure or campus_get_scorm_tracks.

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 guidance, no prerequisites, and no mention of alternatives. The description never clarifies how this differs from other SCORM-related tools in the sibling set, leaving routing entirely to inference from names.

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