Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Count personal UAB SCORM attempts

campus_get_scorm_attempt_count
Read-onlyIdempotent

Counts the authenticated user's attempts for a specific SCORM activity in a given academic year, with an option to include only completed attempts.

Instructions

Count the authenticated user's attempts for one SCORM 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>",
      "scormId": "<scormId>"
    },
    "name": "campus_get_scorm_attempt_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
scormIdYes
completedOnlyNo

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one useful behavioral detail — results are scoped to the authenticated user, with no user parameter to widen scope — but says nothing about how attempts are counted or whether the count is filtered by completion.

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. It is efficient, though the brevity is partly what leaves the parameters 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?

For a simple read-only count tool with annotations and no output schema, the caller mostly knows what to expect. The gap is the two undocumented parameters (year semantics, completedOnly filter), which an agent cannot infer from the description.

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 full burden for the three parameters. It implies scormId ('one SCORM activity') but says nothing about the required year parameter's YYYY-MM format or about completedOnly, which materially changes the count.

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 (Count) and resource (the authenticated user's attempts for one SCORM activity), which is clearly narrower than siblings like campus_get_scorm_tracks or campus_get_h5p_attempts. It is clear enough to distinguish from other SCORM tools without opening the schema, though it never explicitly names an alternative.

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 named alternative for getting full attempt details versus just a count. The intended usage is only implied by the word 'Count' and the singular-activity scope.

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