Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB Group Choice options

campus_get_group_choice_options
Read-onlyIdempotent

Retrieves available groups, capacity counts, and the authenticated user's current selection for a specific Group Choice activity, so you can review options before choosing.

Instructions

Read group options, capacity counts, and only the authenticated user's current selection for one Group Choice activity.

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>",
      "groupChoiceId": "<groupChoiceId>"
    },
    "name": "campus_get_group_choice_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
groupChoiceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context beyond that, and it does: it discloses the return content (options plus capacity counts) and a meaningful privacy constraint — only the authenticated user's selection is visible, not other students' choices. That privacy boundary is exactly the kind of behavioral detail annotations cannot express. It stops short of noting whether capacity counts are live or cached, or what happens for a user with no selection yet.

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 sentence with zero filler; the returned data is front-loaded and the scoping qualifier follows. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates what comes back (options, capacity counts, own selection), which is the main gap it needed to fill for a two-parameter read tool. Remaining gaps are minor: no mention of ordering, pagination, or the empty-selection case.

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 carries the burden for both parameters. It conveys that groupChoiceId identifies the single Group Choice activity being read, which is genuinely useful, but it says nothing about the required year parameter (the yyyy-mm pattern, whether it is an academic or calendar year) and never states that groupChoiceId is the activity identifier explicitly.

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 precisely scoped resource: group options, capacity counts, and the caller's own selection for a single Group Choice activity. The word 'Group' plus 'one Group Choice activity' signals it is a different resource than a plain Choice activity, but it never names or contrasts with the sibling campus_get_choice_options, so the differentiation is only implicit.

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: an agent can infer this is the tool for inspecting one Group Choice activity's options, but there is no explicit when-to-use, no when-not-to-use, and no pointer to campus_get_choice_options or campus_get_my_groups as alternatives. The 'one activity' scoping is a scope constraint rather than guidance on tool selection.

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