Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB assignment submission status

campus_get_assignment_status
Read-onlyIdempotent

Check an assignment's submission, grading, deadline-extension, and attachment status for the authenticated user in a given academic year.

Instructions

Read the authenticated user's submission, grading, deadline-extension, and attachment state for one assignment.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
assignmentIdYes

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 covered. The description adds real value by scoping the read to the authenticated user's own record and by listing the state families returned (submission, grading, deadline extension, attachments). It does not mention behavior when the user has no submission, missing permissions, or how openWorld data staleness affects results.

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 zero filler; every clause names a distinct piece of state the tool returns. Nothing is repeated from the name or annotations.

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?

With no output schema, the description does most of the work by enumerating the state families returned, which is adequate. But for a two-parameter tool with 0% schema coverage it should define the year parameter and at least hint at the no-submission / not-enrolled case.

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 burden for both parameters and largely fails. 'For one assignment' loosely maps to assignmentId, but the 'year' parameter (pattern YYYY-MM, e.g. 2024-25) is never explained - it is ambiguous whether this is an academic year, calendar year, or term, and that ambiguity is exactly what causes wrong calls.

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?

Specific verb plus enumerated state fields; only the sibling boundary is left implicit.

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?

There is no when-to-use / when-not-use guidance and no named alternative. 'For one assignment' implies the single-assignment scope, but an agent gets no signal on whether to call this versus campus_get_assignment_details or campus_get_completion_status for the same assignment.

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