Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB calendar events

campus_get_calendar_events
Read-onlyIdempotent

Retrieve compact Moodle calendar events for selected courses and an optional Unix-time range, including module and activity IDs for assignments and quizzes.

Instructions

Read compact Moodle calendar events for selected courses and an optional Unix-time range. 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_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
timeEndNo
courseIdsNo
timeStartNo
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.2/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that results are 'compact' and that module events carry cmid and instanceId (also surfaced as assignmentId/quizId), which is genuinely useful since there is no output schema. It still omits pagination, result caps (courseIds maxItems 100), and what happens when timeStart/timeEnd are omitted.

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 front-loaded sentences with no filler; the core capability comes first and the return-shape detail second. The parenthetical 'also as assignmentId/quizId' is slightly compressed but still parseable, and nothing is redundant.

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?

For a five-parameter, low-schema-coverage tool with no output schema, the description does some of the necessary lifting (return fields, time semantics) but leaves the meaning of the required 'year' parameter and the default course scope unexplained. An agent could call it, but with avoidable guesswork.

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 20%, so the description must compensate; it partially does by clarifying that courseIds selects courses and that timeStart/timeEnd are Unix-time bounds. It says nothing about 'year' beyond the schema pattern, nor whether an empty courseIds default means all enrolled courses, nor the allowed range of the time bounds.

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?

The description opens with a specific verb and resource: 'Read compact Moodle calendar events for selected courses and an optional Unix-time range.' That is far more precise than the title alone. It does not, however, explicitly distinguish itself from the sibling 'campus_get_calendar_event' (singular), so an agent must infer whether this is the list variant.

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?

There is no guidance on when to use this versus 'campus_get_calendar_event', no statement about prerequisites such as whether 'year' must match enrollment, and no exclusions. The only implied usage is that it lists events for courses within a time range, which the agent must derive from the sentence itself.

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