Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB course forums

campus_list_forums
Read-onlyIdempotent

Read forum metadata for one or more Moodle courses by year and course ID without posting, changing subscriptions, or modifying course content.

Instructions

Read forum metadata for one or more Moodle courses without posting or changing subscriptions.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description's main addition is that it returns metadata only (not posts) and does not touch subscriptions, which is useful but largely restates readOnlyHint. No mention of pagination, result limits, or what happens with courseIds beyond the schema's array bounds.

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 no filler; the scope and read-only constraint come first. It is arguably too terse rather than padded, but nothing is wasted.

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?

With two required parameters, 0% schema description coverage and no output schema, the description needs to carry more. It omits what 'forum metadata' contains, how 'year' is formatted, and any behavior for the courseIds array, so an agent cannot fully call this correctly from the description alone.

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% and the description supplies no parameter meaning at all. The 'year' parameter has a non-obvious '^\\d{4}-\\d{2}$' academic-year format and courseIds caps at 100, yet neither is explained in prose, leaving the agent to infer formats from the raw schema.

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?

Names a specific verb ('Read') and resource ('forum metadata') and scopes it to 'one or more Moodle courses', which separates it from discussion-fetching siblings like campus_get_forum_discussions. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiating.

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?

The phrase 'without posting or changing subscriptions' implies this is the read-only listing path and implicitly excludes write actions, but it never states when to choose this over campus_get_forum_discussions or other forum-related siblings. Usage is only implied.

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