Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Read own UAB assignment submission file

campus_download_submission_file
Read-onlyIdempotent

Retrieve one original file from the authenticated user's current assignment submission as bounded base64 data, with size limits, so clients can download the submission file without broader access.

Instructions

Return one bounded original file from the authenticated user's current assignment submission as base64; 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>",
      "assignmentId": "<assignmentId>",
      "submissionId": "<submissionId>",
      "pluginIndex": "<pluginIndex>",
      "areaIndex": "<areaIndex>",
      "fileIndex": "<fileIndex>"
    },
    "name": "campus_download_submission_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
maxBytesNo
areaIndexYes
fileIndexYes
pluginIndexYes
assignmentIdYes
submissionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds genuinely new information: output is base64-encoded, the file is size-bounded, and the content is untrusted (a prompt-injection safety signal). It does not explain truncation behavior when the bound is exceeded.

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 dense sentence with the resource, scope, return encoding, and trust caveat front-loaded; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with zero schema description coverage and no output schema, this is under-specified: an agent cannot determine which plugin/area/file indices to supply or how the 5 MB default bound behaves. The base64 return value and safety note are covered, but the indexing model is not.

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 7 parameters, so the description carries the full burden — yet it never explains year format, submissionId/assignmentId relationships, or what pluginIndex/areaIndex/fileIndex address. Only 'bounded' loosely hints at maxBytes, leaving the three index parameters completely opaque.

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 one bounded original file from the authenticated user's own assignment submission, encoded as base64. The scope qualifiers ('own', 'current submission') distinguish it from generic resource readers like campus_download_resource, though no sibling is named explicitly.

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 by the scoping language: only the authenticated user's current submission files, and 'bounded' hints at size limits. However, it never states when to use this versus campus_preview_submission or campus_read_assignment_attachment, nor any prerequisite about resolving submissionId first.

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