Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Preview assignment submission eligibility

campus_preview_submission
Read-onlyIdempotent

Inspect assignment rules and your current submission state without uploading files or changing Campus data; use it to preview eligibility and status before submitting.

Instructions

Inspect assignment rules and current personal submission state without uploading or changing Campus data. This does not submit an 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>",
      "courseId": "<courseId>",
      "assignmentId": "<assignmentId>"
    },
    "name": "campus_preview_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes
assignmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/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 the safety profile is covered. The description reinforces the read-only nature and preempts confusion with a submission tool, but adds nothing about auth requirements, what data is returned, or rate/visibility constraints beyond the annotations.

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?

Two short sentences, front-loaded with the core action and immediately followed by the key constraint. The second sentence ('This does not submit an assignment') is somewhat redundant with 'without uploading or changing', but it earns its place by blocking a plausible misinterpretation.

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?

A simple three-parameter read tool with rich annotations, so not much is required, but with no output schema the description should say what a preview returns (eligibility verdict? rule list? current attempt?). It also leaves the 'year' term format and the relationship between courseId and assignmentId unstated.

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% across three required parameters, and the description supplies no meaning for year, courseId, or assignmentId. The names are largely self-explanatory and 'year' is constrained by a YYYY-MM pattern in the schema, but the description makes no attempt to compensate for the coverage gap (e.g., which year format or whether courseId is needed to scope assignmentId).

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: inspect assignment rules plus the caller's own submission state. Clear what it does, but 'rules' and 'submission state' overlap conceptually with siblings such as campus_get_assignment_details and campus_get_assignment_status, and none of those are named to disambiguate.

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 negative guidance is explicit ('does not submit an assignment', 'without uploading or changing'), which implies it is a pre-flight eligibility check. However, there is no positive statement of when to prefer it over campus_get_assignment_status or campus_get_assignment_details, and no prerequisites or exclusions.

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