Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get personal UAB course groups

campus_get_my_groups
Read-onlyIdempotent

Retrieves the authenticated user's group memberships for a specific Moodle course using the academic year and course ID, so you can see which groups they belong to.

Instructions

Read the authenticated user's group memberships in one Moodle course.

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>",
      "courseId": "<courseId>"
    },
    "name": "campus_get_my_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the useful framing that results are limited to the authenticated user and a single course, but says nothing about empty-membership 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 no wasted words; the scope constraint comes first. It is arguably too terse, but nothing is padded or buried.

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?

The tool is simple with two required parameters, rich annotations, and no output schema, so the description need not explain return values. However, with zero schema coverage it should at least identify what 'year' means, which it omits.

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 carries the full burden, yet neither required parameter is mentioned. 'One Moodle course' loosely maps to courseId, but the 'year' parameter with its YYYY-YY pattern is completely unexplained.

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 ('Read') and resource ('group memberships') and constrains scope to the authenticated user in one Moodle course. It is distinguishable from siblings like campus_get_group_choice_options, though it does not name an alternative explicitly.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The phrase 'in one Moodle course' hints at the single-course scope but leaves the agent to infer when this tool is preferable to related group or course tools.

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