purdue-mcp

List Banner registration terms

banner_terms

Retrieve academic terms from Purdue's live registration system, sorted newest first and with 'View only' labels for terms closed to registration.

Instructions

Terms available in Purdue's live registration system, newest first. Terms marked 'View only' are closed to registration. Source: Purdue Banner self-service.

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": "banner_terms"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals data source (Purdue Banner self-service), ordering (newest first), and a specific behavioral detail about 'View only' terms being closed for registration. A minor gap is not stating that this is a read-only operation, though it is strongly implied by 'list' and the context.

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 sentences, perfectly efficient. First sentence states purpose and ordering, second adds behavioral context. No superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no output schema, the description is fully adequate. It tells the agent everything needed: what is returned (terms in registration system), order, source, and a meaningful behavioral property (view-only status). No gaps given the tool's simplicity.

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

Parameters4/5

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

The input schema has zero parameters and 100% description coverage, so schema handles everything. The description adds value by explaining the nature of the data (registration terms, source, ordering, view-only detail) that schema cannot express.

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 clearly states the tool lists banner registration terms from Purdue's live system, including ordering (newest first) and a key behavioral detail (view-only terms). This effectively differentiates it from sibling tools like list_terms which may use a different source or ordering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (when Purdue Banner registration terms are needed) but doesn't explicitly compare to the sibling list_terms tool. It provides good context about data source and behavior but lacks when-not-to-use or alternative guidance.

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