Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get one UAB course module

campus_get_course_module
Read-onlyIdempotent

Retrieve metadata for a single Moodle course module using its course-module ID and academic year, so you can inspect module details available in your enrolled Campus Virtual courses.

Instructions

Read metadata for one Moodle course module by its course-module ID (the id in a mod/...view.php?id= URL, or moduleId from campus_list_resources). Hidden or restricted modules, and modules in courses you are not enrolled in, fail with requireloginerror.

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>",
      "moduleId": "<moduleId>"
    },
    "name": "campus_get_course_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
moduleIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond them by disclosing failure modes: hidden or restricted modules, and modules in courses you are not enrolled in, return requireloginerror.

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 sentences, front-loaded with the verb and resource, followed by the identifier and error semantics. No filler and nothing repeated from the schema or annotations.

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?

There is no output schema, so the description carries the burden of saying what comes back, and "read metadata" is too vague to tell an agent what fields to expect. It handles identification and errors well but leaves both the return shape and the required `year` unexplained.

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

Parameters3/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 parameter meaning and it only half does. moduleId is explained well through its URL origin and the campus_list_resources source, but the required `year` parameter is never mentioned, leaving its format and purpose undocumented everywhere.

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?

The description states a specific verb and resource ("Read metadata for one Moodle course module") and pins the identifier scheme to a course-module ID. It even names where the ID comes from, so an agent can distinguish it from the list/contents siblings without opening the 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?

It gives concrete guidance on when this applies: when you have a moduleId from a mod/...view.php?id= URL or from campus_list_resources. There are no explicit exclusions telling the agent when to prefer campus_get_course_contents instead, but the entry condition is clear.

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