Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get personal UAB SCORM tracking

campus_get_scorm_tracks
Read-onlyIdempotent

Read the authenticated user's completion status, score, and timing tracks for a specific SCORM SCO and attempt.

Instructions

Read the authenticated user's completion, score, and timing tracks for one SCO and attempt.

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>",
      "scoId": "<scoId>"
    },
    "name": "campus_get_scorm_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
scoIdYes
attemptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds that access is limited to the authenticated user's own data, which is useful context, but it says nothing about what a 'track' contains, whether missing data returns empty or errors, or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. Scope and subject are established immediately and every word carries information.

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 read-only, no-output-schema tool this is only partly adequate. It tells the agent what data comes back (completion, score, timing) but omits year formatting, attempt default semantics, and any error or empty-result behavior.

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 the parameter burden. It hints at scoId and attempt ('one SCO and attempt') but leaves the required year parameter (YYY-MM pattern) and the meaning of attempt's default of 0 completely unexplained.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read the authenticated user's completion, score, and timing tracks.' The scoping to 'one SCO and attempt' separates it from siblings like campus_get_scorm_structure and campus_get_scorm_attempt_count without needing to name them.

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?

Implies usage through scope ('the authenticated user's', 'one SCO and attempt'), so an agent can infer this is the per-SCO detail call. However, it never states when to prefer this over campus_get_scorm_structure or campus_get_scorm_attempt_count, and gives no prerequisites or exclusions.

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