Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB Choice options

campus_get_choice_options
Read-onlyIdempotent

Reads the options, availability, and your current selection for a single Moodle Choice in a specified academic year, so you can inspect choice details before responding.

Instructions

Read the options, availability, and authenticated user's current selection for one Moodle Choice.

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>",
      "choiceId": "<choiceId>"
    },
    "name": "campus_get_choice_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
choiceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and repeatability are covered. The description adds one genuine behavioral fact beyond that: the response is user-scoped, including the authenticated user's current selection. It says nothing about what happens when the user has not voted, when the Choice is closed, or when the choiceId is invalid.

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?

A single front-loaded sentence with the verb first and zero filler. Every clause contributes distinct information: the resource, its availability aspect, and the user-specific selection.

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 rich annotations and no output schema, the description covers what is retrieved but leaves the parameter contract entirely unexplained. Given 0% schema coverage on both required params, an agent lacks enough to construct a correct call without outside knowledge.

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 for the two parameters and does not meet it. It never explains what 'year' means (the schema's ^\d{4}-\d{2}$ pattern implies an academic year like 2024-25) or where a caller obtains a valid choiceId, yet both are required.

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 a specific resource set (options, availability, and the authenticated user's current selection) scoped to 'one Moodle Choice'. An agent can tell it retrieves Choice poll data for a single choice. It does not, however, distinguish itself from the near-identical sibling campus_get_group_choice_options.

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?

Usage is only implied: the phrase 'for one Moodle Choice' signals the tool applies when you already have a specific choice in hand. There is no explicit when-to-use statement, no prerequisite (e.g. enrolment/auth requirements), and no routing guidance toward or away from campus_get_group_choice_options.

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