Skip to main content
Glama

UNW calendar

unw_calendar

Retrieve upcoming semester dates, breaks, registration and withdrawal deadlines, and campus events filtered by date to plan academic schedules and campus activities.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
opYesacademic; breaks; deadlines; events
daysNowindow from today in days (default 365 for academic/breaks/deadlines, 7 for events)
limitNorows to return
queryNoacademic/breaks/deadlines: case-insensitive title filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 reasonably well: it discloses the data source (public Google ICS), a 6-hour cache (so results may be stale), that events come from the portal and are filtered by local date, and that the tool is read-only. It does not say whether portal events require authentication or what happens when the upstream calendar is unreachable, which is the main remaining transparency gap.

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?

A single front-loaded sentence naming the resource and its data sources, closed by a short 'Read-only.' tag - dense but every clause carries information. The parenthetical '(public Google ICS, cached 6h)' is slightly packed and interrupts flow, but nothing is redundant.

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 four-parameter read-only tool with no output schema and no annotations, the description covers source, caching, filtering, and safety sufficiently to call it correctly. Remaining gaps are modest: no return-shape hint and no auth/prerequisite note for the portal events path.

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%, so op, days, limit, and query are already documented including the per-op day defaults, making 3 the baseline. The description adds only indirect meaning - that events are filtered by local date and that academic data comes from the ICS feed - without clarifying filter behavior for query or what limit applies to which 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?

Names the resource (academic calendar and campus events) and enumerates the four content types: semester dates, breaks/recesses, registration and withdrawal deadlines, and portal events. It is specific enough to act on, but it does not distinguish itself from the sibling unw_academics, which plausibly covers the same semester/deadline territory, so an agent has to guess between them.

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 scope statements ('academic calendar and campus events', 'filtered by local date') imply when the tool is appropriate, and 'Read-only' signals a safe lookup. There is no explicit when-to-use/when-not-to-use guidance and no mention of the closest sibling (unw_academics) or of how to choose between the academic and events operations beyond the op enum.

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