Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Read one UAB course resource

campus_read_resource
Read-onlyIdempotent

Downloads an identified course-module file and extracts bounded text, so MCP clients can read specific resources while respecting size, character, and PDF-page limits.

Instructions

Download and extract bounded text from one file already identified in a course module.

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_read_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes
maxBytesNo
maxCharsNo
moduleIdYes
fileIndexYes
maxPdfPagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds real value by disclosing that output is text extraction rather than raw bytes and that it is 'bounded', but it never says what the bounds are driven by (maxBytes/maxChars/maxPdfPages), whether truncation is signaled, or how non-text/PDF files behave.

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 zero filler; the scope qualifier follows immediately after the action. It is efficient, though its terseness for a seven-parameter tool borders on under-specification rather than optimal sizing.

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 seven-parameter, four-required tool with no output schema and no parameter documentation, the description does not say how to identify the file, how the size/page limits interact, or what the returned text looks like when truncated. The annotations cover safety, but the identifying and bounding mechanics an agent needs are missing.

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 seven parameters, so the description carries the full burden and largely fails it. 'Bounded' faintly gestures at maxBytes/maxChars/maxPdfPages, but year's YYYY-MM pattern, 0-based fileIndex, and the meaning of courseId vs moduleId 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?

Specific verb pair ('download and extract bounded text') plus a precise resource ('one file already identified in a course module'), which separates it from raw-download siblings by signaling text extraction. It stops short of naming the sibling it supersedes (campus_download_resource), so differentiation is inferential rather than stated.

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?

The only usage signal is the precondition 'already identified in a course module', which hints the caller must first obtain moduleId/fileIndex elsewhere. There is no explicit statement of when to choose this over campus_download_resource or campus_read_assignment_attachment, and no exclusions or prerequisites beyond that phrase.

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