Skip to main content
Glama

myUNW academics

unw_academics

Retrieve read-only University of Northwestern – St. Paul academic records: student profile, GPA, today's classes, schedules by term, grades, holds, registration standing, and degree audit.

Instructions

Academic record: profile/GPA, today's classes, schedule by term, grades by term, official GPA hours, holds, registration standing, and degree audit. Read-only. Times are America/Chicago local; term accepts a Banner code (202610) or name (Fall 2026).

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": {
      "op": "<op>"
    },
    "name": "unw_academics"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesprofile; today; schedule; grades; gpa; holds; registration; degree_audit
termNoschedule/grades only: Banner term code or name; default is the current term / recent graded terms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does add real context: it declares the tool read-only, states that times are America/Chicago local, and explains that term accepts either a Banner code or a term name with a current-term default. It does not disclose authentication requirements, rate limits, or whether sensitive items like holds or GPA are redacted.

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?

The definition is two compact sentences: capabilities first, then operating constraints. Nothing is padded, though the operation list closely mirrors the enum and could have been trimmed without losing information.

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?

For an eight-operation tool with no output schema and no annotations, the description covers inputs and read-only behavior but says nothing about the shape of returned data — e.g. whether grades come back as a list of courses, whether a degree audit is a structured report, or whether results are paginated. That leaves a meaningful gap for a tool of this complexity.

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 coverage is 100%, so both op and term are already documented in the schema. The description's note about Banner codes and the per-op applicability of term largely restates the schema's own parameter text, adding little new meaning beyond the baseline.

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 the concrete resource and enumerates every operation the tool exposes (profile/GPA, today's classes, schedule, grades, holds, registration, degree audit), so an agent knows exactly what domain it covers. It is clearly academic-records specific and does not overlap with siblings like unw_calendar or unw_finances, though it never states that separation explicitly.

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 only usage guidance is the implicit mapping of the listed capabilities to the op enum, plus the note that term applies to schedule/grades only. There is no statement of when to prefer this tool over unw_dashboard or unw_calendar, nor any prerequisite or eligibility conditions.

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