Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB grade overview

campus_get_grade_overview
Read-onlyIdempotent

Retrieve the authenticated user's overall grades for each enrolled subject in a specified academic year, listing course names and kinds, with an option to include non-subject spaces.

Instructions

Read the authenticated user's overall grade for each enrolled subject in one academic year. Each row carries the course name and kind; non-subject spaces (degree coordination, student council, university info) are hidden unless includeNonSubjects is true.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
includeNonSubjectsNo

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 declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description nonetheless adds real behavioral detail the annotations cannot: non-subject spaces (degree coordination, student council, university info) are filtered out unless includeNonSubjects is true, and each row carries the course name and kind.

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, no filler: the read scope and row shape come first, followed by the filtering caveat that affects results. Every clause carries information an agent would otherwise have to guess.

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?

For a read-only, two-parameter tool with no output schema and annotations covering safety, this is nearly complete: scope, row contents, and the hidden-spaces default are all stated. The only shortfall is that the year parameter's expected format is never spelled out in prose.

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. It handles includeNonSubjects well, explaining the default filtering and what enabling it reveals, but it says nothing about the required year parameter beyond implying an academic year, leaving the YYYY-YY format to the regex pattern alone.

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: reading the authenticated user's overall grade per enrolled subject for one academic year. It distinguishes itself from item-level grade tools by saying 'overall grade for each enrolled subject', but it never names a sibling such as campus_get_grades, so the differentiation is implicit rather than explicit.

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 implied by the scoping to one academic year and to per-subject overalls, which suggests this is the summary view rather than a detailed grade lookup. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling grade/course tools.

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