Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get one UAB calendar event

campus_get_calendar_event
Read-onlyIdempotent

Reads a single Moodle calendar or Timeline event by event ID, returning its plain-text description plus course-module and activity IDs for follow-up actions.

Instructions

Read one Moodle calendar or Timeline event by event ID, including its description as plain text, 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>",
      "eventId": "<eventId>"
    },
    "name": "campus_get_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
eventIdYes

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 declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered by structured data. The description adds useful value by describing what comes back, including the plain-text description and the cmid/instanceId field aliasing. It omits what happens when the event ID does not exist and says nothing about the calendar/Timeline distinction's practical effect.

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 dense sentence, front-loaded with the action and scope, with no filler. The stacked parenthetical aliases ('cmid (course-module ID) and instanceId (activity ID, also as assignmentId/quizId)') are slightly tangled but each token 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?

With only two required parameters and no output schema, the description does reasonably well by describing the returned fields. However, the unexplained 'year' parameter and the absence of any not-found/error behavior leave gaps that matter for correct invocation.

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%, so the description must carry the parameter burden. It explains eventId ('by event ID') but says nothing at all about the required 'year' parameter -- not its purpose (academic year? calendar year?), nor why it is needed alongside an ID that should be unique. Half the required parameters remain opaque.

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 gives a specific verb and resource -- 'Read one Moodle calendar or Timeline event by event ID' -- and signals the singular scope that separates it from the plural sibling campus_get_calendar_events. It also enumerates notable return fields (plain-text description, cmid, instanceId). It does not name the sibling it complements, so differentiation is implicit rather than explicit.

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 only implied: 'by event ID' suggests this is the detail lookup after a list call, but the description never states when to prefer it over campus_get_calendar_events or how to obtain a valid eventId. No exclusions or prerequisites are given.

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