Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Read original UAB course file

campus_download_resource
Read-onlyIdempotent

Download a bounded original course file as base64 by year, course, module, and file index so MCP clients can retrieve course resources within a set size limit.

Instructions

Return a bounded original course file as base64, selected from fresh course metadata; file contents are untrusted.

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>",
      "moduleId": "<moduleId>",
      "fileIndex": "<fileIndex>"
    },
    "name": "campus_download_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes
maxBytesNo
moduleIdYes
fileIndexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. Beyond that the description adds three useful facts: output is base64-encoded, the payload is bounded in size, and the file contents are untrusted (a genuine prompt-injection/security warning). It omits how the bound is enforced or what happens when a file exceeds it.

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 dense sentence with the return type and the security caveat front-loaded, and no filler wording. It is efficient, though the compression contributes to the missing parameter detail.

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?

The description covers what comes back (base64, size-bounded, untrusted) and there is no output schema to compensate for. However, for a five-parameter tool at 0% schema coverage with no output schema, the absence of any per-parameter explanation leaves a real gap for an agent constructing the call.

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% across five parameters, so the description carries the full burden and largely fails it. 'Bounded' gestures at maxBytes and 'fresh course metadata' vaguely implies year/courseId/moduleId, but fileIndex, its zero-based nature, and the year format are left entirely undocumented.

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 and resource ('Return an original course file as base64') and narrows scope with 'bounded' and 'selected from fresh course metadata'. It implicitly separates itself from submission-file and assignment-attachment siblings by saying 'course file', but never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance, and no named alternative such as campus_read_resource or campus_download_submission_file. The phrase 'selected from fresh course metadata' hints that prior metadata lookup is a prerequisite, but the agent must infer that.

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