Skip to main content
Glama

myUNW pages

unw_pages

Search myUNW content pages by keyword or read a page by slug for plain-text details on registration, meal plans, and student accounts. Read-only results include excerpts and capped page bodies.

Instructions

Search myUNW content pages and read one by slug (registration, meal plans, student accounts, etc.). Bodies are plain text, capped at 4,000 chars with body_truncated/body_chars. Read-only; no directory or user search.

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

Input Schema

NameRequiredDescriptionDefault
opYessearch; get
slugNoget: page slug, e.g. registration-holds-trad
limitNosearch: rows to return
queryNosearch: words to find
excerpt_charsNosearch: excerpt length (default 120, max 400)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 load and does meaningful work: it declares the tool read-only and discloses that bodies are plain text capped at 4,000 chars, surfacing body_truncated/body_chars so the agent knows it may be reading partial content. It leaves out ordering, pagination behavior beyond the limit field, and what happens on an unknown slug.

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, front-loaded with the primary capability and immediately followed by the return-content caveat and the scope exclusion. No filler or restatement of the tool name.

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 five-parameter read tool with no output schema and no annotations, the definition covers purpose, mode split, scope exclusion, and the return-value truncation contract. Only error/empty-result behavior and result ordering are unaddressed, which is a minor gap.

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%, so every parameter (op, slug, query, limit, excerpt_chars) is already documented in the schema, establishing a baseline of 3. The description's 'read one by slug' reinforces the slug parameter's role but adds no format or constraint detail beyond the structured fields.

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 verb pair and resource: 'Search myUNW content pages and read one by slug', and enumerates the content domains (registration, meal plans, student accounts). It also scopes negatively ('no directory or user search'), so an agent can rule it out for people-lookup without opening the schema.

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 two operating modes are stated and each schema parameter is prefixed with 'search:' or 'get:', making it clear which inputs belong to which mode. It stops short of explicit when-to-use/when-not guidance beyond the directory/user exclusion, so it is clear context rather than full routing rules.

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