Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB assignments

campus_list_assignments
Read-onlyIdempotent

Lists assignment IDs, due dates, grades, and submission rules for selected Moodle courses in a given academic year; use it to scan course assignments and identify where full details are needed.

Instructions

Read assignment IDs, dates, grades, and submission rules for one or more Moodle courses. Intros are shortened; use campus_get_assignment_details for full instructions.

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>",
      "courseIds": "<courseIds>"
    },
    "name": "campus_list_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: intros are truncated, and the full text lives behind campus_get_assignment_details. It says nothing about result volume or whether the 100-course cap affects output, which keeps it from 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 short sentences, front-loaded with what is returned, followed by the caveat and the redirect. Nothing is redundant and every clause carries information.

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 return-shape summary compensates well for the absent output schema, and the truncation caveat is valuable. However, for a two-parameter, both-required tool with zero schema descriptions, leaving 'year' entirely unexplained is a real completeness gap an agent must guess around.

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%, and both parameters are required, so the description carries the burden. 'One or more Moodle courses' loosely maps to courseIds, but the required 'year' parameter is never mentioned at all — no indication of its format (YYYY-MM) or what it selects. That leaves a required parameter unexplained in both the schema and the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Read') plus the resource (assignments) and enumerates returned fields: IDs, dates, grades, submission rules. It also scopes the operation ('for one or more Moodle courses') and explicitly separates itself from campus_get_assignment_details, so an agent can pick it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing rule to the sibling when full instructions are needed, which covers the main ambiguous case. It stops short of stating exclusions (e.g., that it is not the place to look for submission status or per-student grades), so it is clear context rather than a complete use/don't-use matrix.

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