Skip to main content
Glama

myUNW finances

unw_finances

Retrieves read-only University of Northwestern–St. Paul student account and dining balances, chapel credit, and financial-aid awards with cost of attendance for the active aid year.

Instructions

Student account and dining-funds balances, chapel/spiritual-development credit, and financial-aid awards plus cost of attendance for the active aid year. Read-only; amounts are in USD.

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_finances"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesbalances; financial_aid; chapel
aid_yearNofinancial_aid only: aid year code (2627) or label (2026-2027); default is current

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and it does deliver two useful behavioral facts: 'Read-only' and 'amounts are in USD'. It stops short of stating that results are scoped to the authenticated student, whether financial-aid awards can be partially withheld, or anything about freshness of balances — gaps that matter for a tool returning money figures.

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, with the substantive scope front-loaded and the behavioral caveat (read-only, USD) trailing compactly. Nothing is wasted, though the opening lacks a verb that would make the intent instantly parseable.

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?

There is no output schema and no annotations, so the description is the only place an agent can learn what comes back. It enumerates the data domains but does not sketch the shape of each op's result (e.g. a single balance figure vs. a list of awards with amounts and cost of attendance), leaving a multi-op tool under-described on the return side.

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% and the enum plus aid_year description already document accepted formats ('2627' or '2026-2027') and the current-year default. The description adds only the framing that the aid year is 'active', so it neither compensates for nor exceeds what the schema already provides — baseline 3.

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 resources covered — student account and dining-funds balances, chapel/spiritual-development credit, and financial-aid awards plus cost of attendance — which map directly onto the three op enum values. That is specific and unambiguous, though the noun-phrase framing lacks an explicit verb and it never distinguishes itself from the sibling unw_dining, which plausibly overlaps with 'dining-funds balances'.

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 three listed domains implicitly tell an agent which op to pick, and 'for the active aid year' hints that aid_year binds to the current year by default. However, there is no explicit when-to-use statement, no exclusion of the sibling tools, and no pointer to unw_dining for meal-plan or transaction-level questions.

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