Skip to main content
Glama
umich-dining-mcp

umich-dining-mcp

by esreddy2

List dining halls

list_locations
Read-onlyIdempotent

Lists University of Michigan dining halls and their daily service periods, including whether each is open now, with optional date and hall filters.

Instructions

List the dining halls and their service periods for the day, with whether they are open now. openNow is evaluated at the current campus-local time. The entries are the halls and their service periods for the day. stale means a page was served from an expired cache entry; asOf is the age of the data. Cafes, markets, bakeries, grills, prices and meal plans are out of scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day to read. Defaults to today.
hallNoKeep only this hall.

Output Schema

NameRequiredDescriptionDefault
dateYes
failuresYes
locationsYes
mapUrlTemplateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • removedInput schema / properties / hall / enum
      Removed value: -[
      -  "bursley",
      -  "east-quad",
      -  "markley",
      -  "mosher-jordan",
      -  "north-quad",
      -  "south-quad",
      -  "twigs-at-oxford",
      -  "wolverine-village",
      -  "lawyers-club",
      -  "martha-cook"
      -]
  2. Changed13 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date in YYYY-MM-DD. The site publishes menus for today-3 days to today+14 days."New value: +"The day to read. Defaults to today."
    • addedInput schema / properties / hall
      Added value: +{
      +  "description": "Keep only this hall.",
      +  "enum": [
      +    "bursley",
      +    "east-quad",
      +    "markley",
      +    "mosher-jordan",
      +    "north-quad",
      +    "south-quad",
      +    "twigs-at-oxford",
      +    "wolverine-village",
      +    "lawyers-club",
      +    "martha-cook"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / locations / items / properties / asOf
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / locations / items / properties / date
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / locations / items / properties / mapUrl
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / locations / items / properties / meals
      Removed value: -{
      -  "items": {
      -    "enum": [
      -      "Breakfast",
      -      "Lunch",
      -      "Dinner"
      -    ],
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / locations / items / properties / path
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / locations / items / properties / today / items / required
      Previous value: -[
      -  "label",
      -  "times",
      -  "closed"
      -]New value: +[
      +  "label",
      +  "times"
      +]
    • changedOutput schema / properties / locations / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "path",
      -  "url",
      -  "residentsOnly",
      -  "glutenFreePantry",
      -  "address",
      -  "phone",
      -  "email",
      -  "mapUrl",
      -  "meals",
      -  "date",
      -  "today",
      -  "openNow",
      -  "stale"
      -]New value: +[
      +  "id",
      +  "name",
      +  "url",
      +  "residentsOnly",
      +  "glutenFreePantry",
      +  "address",
      +  "phone",
      +  "email",
      +  "today",
      +  "openNow",
      +  "stale"
      +]
    • addedOutput schema / properties / mapUrlTemplate
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / warning
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "date",
      -  "locations",
      -  "failures",
      -  "warning"
      -]New value: +[
      +  "date",
      +  "locations",
      +  "failures"
      +]
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses meaningful runtime behavior: openNow is computed at campus-local time, and it explains the stale/asOf response fields as cache-age signals. This is real added context an agent could not get from annotations. It does not mention caching TTL or freshness guarantees the agent might rely on when choosing stale data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope and time semantics are front-loaded, but the sentence 'The entries are the halls and their service periods for the day' restates the opening clause almost verbatim. With an output schema present, that redundancy costs space without adding information.

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 zero-required-param, read-only listing with an output schema, the description covers scope, time zone semantics, cache metadata, and exclusions. The main remaining ambiguity is how a supplied date interacts with 'open now' — whether openNow reflects today or the requested day — which an agent may need in order to call it correctly.

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 coverage is 100%, so both parameters (date, hall) are already documented with formats and defaults. The description adds only 'for the day' framing and does not clarify how date interacts with the openNow computation. Baseline 3 for full schema coverage.

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?

States a specific verb and resource with scope: 'List the dining halls and their service periods for the day, with whether they are open now.' It also draws a boundary against adjacent content (cafes, markets, prices, meal plans). It stops short of distinguishing itself from siblings like get_hours and find_open_now, which overlap heavily with 'service periods' and 'open now'.

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 is only implied: the agent can infer this is the all-halls overview for a given day. Out-of-scope items are enumerated, which partially serves as a when-not list, but no alternative sibling is named for filtering to a single hall's hours or for finding open venues.

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