Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UNW_MCP_HEADLESSNoWhether Chromium runs headless. Set to false only when a display/Xvfb is available.true
UNW_MCP_TIMEZONENoTimezone used for all rendering, event windows, and today's classes.America/Chicago
UNW_MCP_CONFIG_DIRNoDirectory for configuration files. Precedence is environment > ~/.config/unw-mcp/config.yaml > defaults.
UNW_MCP_PROFILE_DIRNoDirectory for the persistent Chromium browser profile. Defaults to ~/.config/unw-mcp/browser-profile.
UNW_MCP_*_TTL_MINUTESNoPer-cache TTL overrides in minutes. The README documents this environment-variable pattern; exact names are in .env.example.
UNW_MCP_REAUTH_TIMEOUT_MSNoReauthentication timeout in milliseconds.
UNW_MCP_REQUEST_TIMEOUT_MSNoRequest timeout in milliseconds.
UNW_MCP_NAVIGATION_TIMEOUT_MSNoNavigation timeout in milliseconds.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
unw_sessionA

Check the myUNW portal session or force re-authentication. status probes the live API and reports cookie lifetimes; reauth reloads the persistent browser profile (silent SAML ~10s, then credentials+TOTP if Entra expired). No portal data is modified.

unw_dashboardA

Student dashboard. day is the plan-my-day view: today's classes, next-24h campus events, pending tasks and the next meal with a few options. overview adds identity/degree progress and announcements; announcements/tasks/events/quick_links return one list. Read-only.

unw_academicsA

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).

unw_financesB

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.

unw_diningA

Campus dining menus: locations, one day's cafes/dayparts/stations/items, or a compact 7-day overview. Public data, cached hourly; never returns the raw menu payload.

unw_calendarA

Academic calendar and campus events: upcoming semester dates, breaks/recesses, registration and withdrawal deadlines (public Google ICS, cached 6h), plus portal campus events filtered by local date. Read-only.

unw_pagesA

Search myUNW content pages and read one by slug (registration, meal plans, student accounts, etc.). Bodies are plain text, capped at 4,000 chars with body_truncated/body_chars. Read-only; no directory or user search.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation3/5

The core domains (session, academics, finances, dining, calendar, pages) are distinct, but unw_dashboard's 'day' view deliberately re-aggregates data that also lives in unw_academics (today's classes), unw_calendar (campus events), and unw_dining (next meal), so an agent asking about 'today' has several plausible entry points. Descriptions do explain the aggregator role, but the boundaries between dashboard and the domain tools remain blurry in practice.

Naming Consistency4/5

All seven tools use a uniform 'unw_' prefix followed by a single domain noun, which is predictable and readable. Minor deviation: plurality is inconsistent (academics/finances/pages are plural while session/dashboard/dining/calendar are singular), and the pattern is resource-oriented rather than verb_noun, so actions are only discoverable via descriptions.

Tool Count5/5

Seven tools is well within the sweet spot and each maps to a genuine portal area (auth, dashboard, academics, finances, dining, calendar, pages). No tool feels redundant as a standalone resource, and the surface is compact enough for an agent to hold in context.

Completeness4/5

The read-only lifecycle is well covered: authentication handling, academic records, balances, dining menus, calendar/deadlines, and content pages. Gaps exist for a student portal — no course/catalog search to support registration, no messages/inbox, and no task creation or completion despite dashboard surfacing pending tasks — but these are workable omissions for a read-only surface.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues