Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB grades

campus_get_grades
Read-onlyIdempotent

Retrieve grade items for a specific Moodle course and academic year from the authenticated user's Campus Virtual account to review assessment results.

Instructions

Read the authenticated user's grade items for one Moodle 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_get_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds useful context that results are scoped to the authenticated user (no user parameter, no cross-user reads) and to a single course, but says nothing about grading visibility, unpublished items, or result shape.

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 filler; the scope constraints appear before anything else. It is efficient, though arguably too terse for a tool with a completely undocumented parameter.

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

Completeness2/5

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

With two required parameters at 0% schema coverage, no output schema, and no annotation-level detail about grading semantics, the description leaves the meaning of 'year' entirely unexplained and gives no sense of what a 'grade item' contains. For a two-parameter tool this is not complete enough to guarantee a correct invocation.

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. It implicitly clarifies that courseId identifies the Moodle course and that no user identifier is needed, but the required 'year' parameter (pattern ^\d{4}-\d{2}$) is never explained – an agent cannot tell whether that is an academic year, a term label, or a date range.

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?

The description names a specific verb and resource ('Read ... grade items') plus a clear scope: the authenticated user's own grades, restricted to one Moodle course. That scope distinguishes it in spirit from a course-wide grade overview, but it never names a sibling explicitly, so an agent must infer the boundary.

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?

The phrase 'for one Moodle course' implies the per-course drill-down case, which is a weak usage signal. There is no explicit when-to-use/when-not-to-use statement and no pointer to campus_get_grade_overview for the aggregate case, so routing must be inferred.

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