unw-mcp

Overview Schema Source Related Servers Discussions Admin

unw_search

Search a term's course sections by subject, number, keyword, instructor, attribute, or availability, then page through cached results to find CRNs, meeting times, seats, and faculty.

Instructions

Search one term's sections (normalised rows: CRN, course, title, credits, seats, days/times, faculty, attributes, availability). Banner ignores the attribute/instructor/open-only query parameters, so filtering happens client-side over a cached term snapshot. limit is capped at 200; when limit_capped is true follow next_offset to page through the rest.

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": {
      "term": "<term>"
    },
    "name": "unw_search"
  }
}

Input Schema

Name	Required	Description	Default
`term`	Yes
`limit`	No
`number`	No
`offset`	No
`keyword`	No
`refresh`	No
`subject`	No
`attribute`	No
`open_only`	No
`instructor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

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 real work: it discloses the important quirk that Banner ignores attribute/instructor/open_only parameters and filtering is applied client-side over a cached snapshot, plus the 200-item cap and the limit_capped/next_offset paging contract. It stops short of explaining cache staleness or what the `refresh` flag changes, which matters for a cached-snapshot tool.

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?

Three dense sentences, front-loaded with purpose then caveats then paging. The parenthetical field list is long but earns its place by defining the return payload in the absence of an output schema; no filler sentences.

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?

For a 10-parameter read tool with no annotations and no output schema, the description covers the behavioral traps (ignored params, caching, cap, paging) but omits term identifier format, refresh semantics, and the meaning of most filter parameters, leaving an agent to guess at call syntax.

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

Parameters2/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate; it covers `limit` (cap 200) and partially explains attribute/instructor/open_only, but leaves `term` (format-critical and required), `keyword`, `number`, `subject`, `offset`, and `refresh` entirely undefined. Half the parameters remain opaque even after reading the description.

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?

States a precise verb+resource ("Search one term's sections") and then enumerates the returned row shape (CRN, course, title, credits, seats, days/times, faculty, attributes, availability), which makes it unmistakable against siblings like unw_course or unw_session that operate on a single entity rather than a term-wide section list.

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 context is implied by the required `term` and the note that filtering is client-side over a cached snapshot, but there is no explicit statement of when to choose this over unw_course, unw_offering_matrix, or unw_remaining, and no exclusions.

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