Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB Choice activities

campus_list_choices
Read-onlyIdempotent

Retrieves Moodle Choice activities and their availability rules for a UAB Campus Virtual course and academic year, enabling review of choices and access conditions.

Instructions

Read standard Moodle Choice activities and their availability rules for one 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_list_choices"
  }
}

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 read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that availability rules are included in the result, which is real value, but it says nothing about pagination, result size, or what happens for a course with no Choice activities.

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 wording. It is arguably too terse rather than bloated, but structure and clarity are good.

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 simple two-parameter read with no output schema, the description covers purpose and scope but leaves the required year parameter entirely unexplained and gives no sense of the return shape beyond 'availability rules'. Adequate but with clear gaps.

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 must carry parameter meaning. It only implies courseId via 'for one course' and never mentions the required 'year' parameter or its YYYY-MM format, leaving the agent to reverse-engineer that from the schema pattern.

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 standard Moodle Choice activities and their availability rules') plus scope ('for one course'), which distinguishes it from the get_choice_options siblings that fetch a single activity's options. 'Standard' is slightly vague but the core purpose is unambiguous.

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?

No when-to-use or when-not-to-use guidance, and no mention of any alternative such as campus_get_choice_options or campus_get_group_choice_options. The agent has to infer that this is the discovery step before fetching options.

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