Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Read one UAB assignment attachment

campus_read_assignment_attachment
Read-onlyIdempotent

Download and extract bounded text from a single assignment-instruction attachment by file index, so you can read starter code, PDFs, or statements without fetching unrelated files.

Instructions

Download and extract bounded text from one file attached to an assignment's instructions (introattachments, e.g. starter code or a statement PDF). The file is resolved through the assignment API by its fileIndex; content is 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>",
      "assignmentId": "<assignmentId>",
      "fileIndex": "<fileIndex>"
    },
    "name": "campus_read_assignment_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes
maxBytesNo
maxCharsNo
fileIndexYes
maxPdfPagesNo
assignmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real value by disclosing that output is bounded/truncated text, that the file is fetched via the assignment API, and that content is untrusted. It does not say what happens on truncation or how failures surface, which keeps it below a 5.

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?

Two sentences, zero filler, with the scope and the extraction behavior front-loaded and the trust caveat trailing as a brief warning. Nothing is repeated from the schema or annotations.

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 7-parameter, 4-required read tool with no output schema and no parameter descriptions, the definition covers purpose and trust but omits the identifiers needed to call it correctly and any indication of the response shape (text only, metadata, truncation flags). Adequate to select the tool, thin for invoking it precisely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description had to compensate and only partially does: fileIndex is tied to the assignment API and 'bounded text' loosely gestures at maxBytes/maxChars/maxPdfPages. The meanings of year, courseId, assignmentId and each cap parameter are left entirely to the schema's types and defaults.

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?

A concrete verb pair ('download and extract bounded text') plus a tightly scoped resource ('one file attached to an assignment's instructions (introattachments)'). The parenthetical examples (starter code, statement PDF) and the introattachments scope distinguish it reasonably well from submission-file or generic resource readers, though no sibling is named directly.

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?

Usage is implied rather than stated: 'resolved through the assignment API by its fileIndex' suggests you must first obtain fileIndex elsewhere (likely assignment details), but it never says when to pick this over campus_download_resource or campus_download_submission_file. No prerequisites or exclusions are given.

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