Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB forum discussions

campus_get_forum_discussions
Read-onlyIdempotent

Read discussions from one Moodle forum without posting or changing subscriptions; root messages are shortened, so fetch full text separately.

Instructions

Read one Moodle forum's discussions without posting or changing subscriptions. Root messages are shortened; use campus_get_discussion_posts for full text.

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>",
      "forumId": "<forumId>"
    },
    "name": "campus_get_forum_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
yearYes
forumIdYes
perPageNo
sortOrderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely new behavior: root messages are truncated, which materially affects how an agent should interpret results. It says nothing about pagination defaults or rate/scope limits, keeping it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the primary action and followed by the disambiguation. Every clause carries information; nothing is padding.

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 read-only listing tool with no output schema, the description covers purpose, the truncation caveat and the sibling route. However, with five undocumented parameters and no note on result ordering or paging, an agent cannot call it correctly without guessing at the schema.

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% across five parameters, including an ambiguous 'year' with a YYYY-MM pattern and page/perPage/sortOrder controls. The description mentions none of them, so an agent gets no help on what 'year' means or how paging behaves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one Moodle forum's discussions') and immediately delimits scope against the sibling ('use campus_get_discussion_posts for full text'). An agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative tool and the condition that selects it (full text needed), and rules out posting/subscription changes. It stops short of guidance on pagination or when to prefer this over browsing course contents, but the key routing decision is covered.

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