Skip to main content
Glama

UNW dining

unw_dining

Retrieve campus dining menus by location, day, meal, or 7-day overview. Filter cafes and dates to find breakfast, lunch, or dinner items without raw menu payloads.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
opYeslocations; today (one day); week (7 rolling days)
cafeNofilter by cafe name or id (case-insensitive substring)
dateNotoday/week: start date; default is today in the configured zone
mealNotoday/week: only this daypart (case-insensitive substring)
detailNotoday: brief (6 stations × 8 items) or full (configured caps)brief

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 does disclose meaningful traits: the data is public (no auth implied), results are cached hourly (so up to an hour stale), and the tool deliberately never returns the raw menu payload. That is real behavioral context an agent could not get from structured fields. It stops short of stating error behavior for invalid cafe names or out-of-range dates.

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?

Two short sentences with no filler; the resource and its three modes are front-loaded, and the behavioral caveats (caching, condensed output) follow in a compact second clause. Every phrase carries information.

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?

With five parameters, three modes, and no output schema, the description should say more about the shape of what comes back — 'compact 7-day overview' and 'cafes/dayparts/stations/items' hint at structure but do not define it. The behavioral side is adequately covered, but the returned payload for each op remains underspecified.

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 three parameters are enums, so the schema already documents op, cafe, date, meal, and detail thoroughly, including the brief/full caps. The description adds essentially nothing beyond that, so the baseline 3 applies rather than a higher score.

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 names a specific resource (campus dining menus) and enumerates the three concrete shapes it can take: locations, one day's cafes/dayparts/stations/items, and a compact 7-day overview. That mapping to the op enum makes the tool's scope unambiguous, and the sibling tools (academics, calendar, finances, pages, session) share no overlapping domain, so no further differentiation is needed.

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 modes are listed, which implies which op suits which request, but there is no explicit when-to-use guidance such as 'use week when planning ahead, today when you need item-level detail.' There are no exclusions, prerequisites, or failure conditions stated, so the agent must infer mode selection from the schema enum alone.

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