Skip to main content
Glama
Sign In
unw-mcp

unw-mcp

by HenryGetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unw_terms

Retrieve Banner term codes, descriptions, and registration eligibility flags; refresh cached eligibility to re-probe Banner when needed.

Instructions

Banner term codes with descriptions plus is_next, is_current, view_only and registration_eligible flags. Eligibility is probed through Banner's own mode=registration response (cached per process); refresh=True re-probes it. Failures are included verbatim.

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

Input Schema

NameRequiredDescriptionDefault
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses that eligibility comes from probing Banner's mode=registration endpoint, that results are cached per process, that refresh=True forces a re-probe, and that failures are surfaced verbatim. It does not say whether the probe is read-only in effect or how expensive it is, so not a 5.

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 tight sentences, front-loaded with the returned fields, then caching/refresh, then failure handling. Dense with no filler, though 'mode=registration' is jargon that assumes Banner familiarity.

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 no-output-schema, single-param lookup the description covers return fields, caching, the refresh trigger, and failure output. Missing only auth/prerequisite context and any indication of when term codes are preferred over sibling data sources.

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?

Schema coverage is 0% for the single parameter, so the description must compensate, and it does: refresh=True is explained as re-probing the cached registration eligibility, with the default implication of using the cache. That is the only semantic an agent needs for this boolean.

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?

The description names the resource concretely ('Banner term codes with descriptions') and enumerates the per-term flags returned, so an agent knows exactly what data this yields. It lacks an explicit verb and never contrasts itself with siblings like unw_registration_window or unw_offering_matrix, which keeps it short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use statement and no named alternative; the agent must infer that this is the lookup for term codes needed by registration and plan tools. The only usage-like content is the refresh=True re-probe note, which is really parameter behavior rather than guidance on selecting this tool.

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

Deploy Server

Other Tools