Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get upcoming UAB actions

campus_get_upcoming_actions
Read-onlyIdempotent

Retrieve upcoming actionable Moodle events ordered by due time, each with course-module and activity IDs. Use it to prioritize what needs attention next in UAB Campus Virtual.

Instructions

Read compact upcoming actionable Moodle events ordered by due time. Each module event carries cmid (course-module ID) and instanceId (activity ID, also as assignmentId/quizId).

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

Input Schema

NameRequiredDescriptionDefault
fromNoUnix time to start from; defaults to now.
yearYes
limitNo
includeDescriptionsNoInclude each event's description as plain text (omitted by default to keep lists small).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely useful context about result shape and ordering that annotations cannot convey. However, it says nothing about paging behavior beyond the implicit limit, how far 'upcoming' extends, or what happens when the year argument doesn't match the from time.

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 tight sentences with the primary purpose front-loaded and the identifier aliasing packed into the second. No filler, no restatement of the title.

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?

With no output schema, the description usefully explains the returned identifiers and ordering, which is the main thing an agent needs to chain into detail tools. It falls short on the required year parameter's format and on how results are bounded, so an agent must open the schema to call it correctly.

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 coverage is only 50%, and the single required parameter, year (pattern ^\d{4}-\d{2}$), has no description anywhere in schema or prose. The description's only field-level detail (cmid, instanceId) concerns output, not inputs, so it does not compensate for the undocumented required parameter.

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 ('Read compact upcoming actionable Moodle events') plus ordering ('by due time'), so the agent knows it is a cross-course upcoming-events list rather than a details fetcher. It does not name or contrast with the nearest sibling, campus_get_course_actions, so the distinction from course-scoped variants must be inferred.

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?

'Upcoming actionable' and 'ordered by due time' imply the use case (finding what's due next), but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent to prefer campus_get_course_actions when it only cares about one course, or campus_get_calendar_events for non-actionable entries.

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