Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get actionable UAB course events

campus_get_course_actions
Read-onlyIdempotent

Read compact actionable Moodle events for one course in the authenticated user's account within explicit time bounds and paging, returning module and activity IDs for follow-up actions.

Instructions

Read the authenticated user's compact actionable Moodle events for one course with explicit time bounds and paging. 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>",
      "courseId": "<courseId>"
    },
    "name": "campus_get_course_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNoUnix time to start from; defaults to now.
yearYes
limitNo
searchNo
courseIdYes
afterEventIdNo
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are 'compact' and that each event carries cmid and instanceId (also surfaced as assignmentId/quizId), which is genuinely useful payload context since there is no output schema. It says nothing about ordering, paging continuation via afterEventId, or rate/limit behavior.

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?

Two dense sentences with the scoping and time/paging constraints front-loaded; nothing is wasted. The second sentence earns its place by describing returned event fields that are otherwise undocumented.

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

Completeness4/5

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

Eight parameters at 25% schema coverage and no output schema put the burden on the description, and it does cover scope, time bounds, paging intent, and the key payload identifiers. Gaps remain around year format, search semantics, and paging resumption, but the core of a correct invocation is conveyed.

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 only 25% (from and includeDescriptions only), so the description must carry weight. It mentions 'explicit time bounds and paging', which loosely maps to from/to/limit/afterEventId, but it does not explain the unusual YYYY-MM 'year' string, the role of 'search', or how afterEventId resumes a page.

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 the authenticated user's actionable Moodle events scoped to one course, with time bounds and paging. The course-scoped, action-only framing implicitly separates it from cross-course siblings like campus_get_upcoming_actions, though no sibling is named.

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 'for one course' and 'actionable events', which tells the agent this is the per-course action feed rather than a general calendar or content listing. However, there is no explicit when-to-use/when-not statement and no alternative tool is named for the cross-course case.

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