Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB SCORM structure

campus_get_scorm_structure
Read-onlyIdempotent

Read the organizations and SCO items of a SCORM package without launching it, enabling you to inspect its structure by year and scormId.

Instructions

Read the organizations and SCO items contained in one SCORM package without launching it.

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>",
      "scormId": "<scormId>"
    },
    "name": "campus_get_scorm_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
scormIdYes
organizationNo

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 readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds the useful detail that reading does not trigger a launch/attempt, but says nothing about return shape or how organizations relate to SCO items.

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 wasted words. It is efficient, though its brevity contributes to the parameter gaps noted elsewhere.

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?

For a three-parameter read tool with rich annotations and no output schema, the description is adequate on purpose but incomplete on parameters. The undocumented organization parameter and year format leave real gaps an agent would need to resolve.

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 it largely fails. It implies scormId via 'one SCORM package' but never explains the year format (YYYY-MM) or the purpose of the optional organization parameter.

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 (organizations and SCO items in a SCORM package) with clear scope (one package). The 'without launching it' clause distinguishes it from actually playing the package, though it does not name a specific sibling tool.

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 phrase 'without launching it' implies this is the inspection-only path versus launching the package, giving some when-to-use signal. However, no explicit alternatives or exclusions are named, so the agent must infer the boundary.

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