Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB notifications

campus_list_notifications
Read-onlyIdempotent

Read your Moodle notifications for a specified academic year without marking them as read, with pagination and newest-first ordering.

Instructions

Read the authenticated user's Moodle notifications without marking them as read.

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_list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
limitNo
offsetNo
newestFirstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint; the description earns credit by adding the non-obvious guarantee that fetching does not alter read state, which is a real side effect of many notification APIs. It stops short of describing pagination behavior or result shape.

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 front-loaded sentence with zero filler, and the key behavioral constraint is placed where it will be read first. Its brevity is appropriate in form, though it leaves no room for the parameter context this tool needs.

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

Completeness2/5

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

For a four-parameter paginated list tool with an undocumented required period parameter and no output schema, the description is far too thin — an agent cannot tell what 'year' means or how to page through results. It is saved only by rich annotations that establish the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, including the required 'year' with a YYYY-MM pattern whose meaning (academic year? calendar period?) is never explained. limit/offset/newestFirst are likewise undocumented in both schema and description, so the description adds no parameter meaning at all.

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 ... Moodle notifications') scoped to the authenticated user, which is unambiguous. It does not need to differentiate from siblings since none of the listed siblings list notifications, but it also never says so explicitly.

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 the name and the phrase 'without marking them as read', which signals a non-mutating fetch rather than a mark-as-read operation. There is no explicit when-to-use guidance, no mention of auth prerequisites (campus_auth_status), and no exclusions.

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