Skip to main content
Glama

myUNW session

unw_session

Check the student portal session or force re-authentication: probe live API cookie lifetimes, or restore the browser profile when SAML/Entra credentials expire without modifying portal data.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
opYesstatus: live probe + cookie lifetimes; reauth: restore the session, then report

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that status makes a live API call, that reauth drives a persistent browser profile, the ~10s silent SAML path, the fallback to credentials plus TOTP, and the important safety claim that no portal data is modified. It stops short of describing failure modes or what happens if reauth itself fails.

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?

Three tight sentences, front-loaded with the overall purpose, then per-op detail, then the non-destructive guarantee. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single enum parameter with no output schema, the definition covers purpose, both modes, timing, auth requirements, and the non-mutation guarantee. The only gap is how results are presented (format of the cookie-lifetime report) and failure behavior, which is minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the prose adds real meaning beyond the schema's terse op descriptions: reauth's cost (~10s), its silent-SAML-first behavior, and the TOTP escalation. That materially helps an agent decide whether to invoke the heavier mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Check the myUNW portal session or force re-authentication') and immediately disaggregates the two operations. It is clearly distinguishable from the sibling tools (academics, calendar, finances), which all fetch portal data, since this one manages the session itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the role of each op: status probes the live API and reports cookie lifetimes, while reauth reloads the profile to restore the session. That gives clear context for choosing between the two modes, but there is no explicit sequencing advice (e.g. probe first, reauth only if expired) and no when-not-to-use exclusions.

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