Skip to main content
Glama

myUNW dashboard

unw_dashboard

Retrieve a read-only student dashboard covering daily classes, upcoming events, pending tasks, next meal, degree progress, announcements, and quick links from the university portal.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
opYesoverview: identity + 3 notices + 5 tasks + today; day: classes + 24h events + tasks + next meal; announcements; tasks; events; quick_links
daysNoevents only: today + N days (default 7)
limitNorows to return (default per op)
include_completedNotasks only: include completed items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and 'Read-only.' is a genuinely useful disclosure that no structured field provides. It also conveys what data surfaces in each view (today's classes, next-24h events, next meal). It says nothing about authentication/student scoping, rate limits, or what happens when no data exists, which matters for a six-op aggregator with zero annotation coverage.

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?

Compact and front-loaded: the 'day' view, the most distinctive mode, is explained first and each remaining op gets a short clause. The semicolon-chained sentence is dense but earns its place; only minor tightening is possible.

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 read-only aggregation tool with a fully documented four-parameter schema and no output schema, the description covers every op and its scope. The remaining gaps (op/parameter interaction rules, empty-result behavior, scoping) are modest relative to the tool's 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 description coverage is 100% and the op enum already documents each mode's payload, so the description mostly restates the schema. It adds mild value by describing the quality of content ('the next meal with a few options'), but it does not clarify how 'days' and 'limit' interact or what happens when 'days' is passed with a non-events op.

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 a concrete resource (student dashboard) and spells out what each of the six ops returns, including the distinguishing detail that 'day' is the plan-my-day composite view. It stops short of contrasting with the sibling tools (unw_calendar, unw_dining, unw_academics), so an agent must infer whether a dashboard call or a domain call is right.

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?

Usage guidance exists only at the op level: 'day' vs 'overview' vs the single-list ops, which implies when to pick each mode. There is no statement about when to prefer this aggregate tool over the sibling domain tools, 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.