unw-mcp

Overview Schema Source Related Servers Discussions Admin

unw_ratings

Look up Rate My Professors ratings for multiple professors by name, flag weak evidence when fewer than three reviews exist, and refresh cached results on demand.

Instructions

Batch Rate My Professors lookup. Accepts "Last, First" or "First Last". Unrated professors return rating=null (never 0.0); weak_evidence flags n<3. Cache entries expire after 7 days; refresh=True refetches now. Transient RMP failures are never cached.

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": {
      "names": "<names>"
    },
    "name": "unw_ratings"
  }
}

Input Schema

Name	Required	Description	Default
`names`	Yes
`refresh`	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 substantial work: it discloses null-vs-zero semantics (rating=null, never 0.0), the weak_evidence threshold (n<3), 7-day cache expiry, and that transient RMP failures are never cached. It omits batch-size limits and per-name error handling, which are the remaining behavioral gaps.

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?

Four dense sentences with the core purpose and input format front-loaded and the caching/edge-case semantics following logically. Minor waste from literal double-backtick markup around refresh=True, but 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?

There is no output schema, so the description is the only source of return-value information, and it covers only two fields (rating, weak_evidence) without describing the overall result shape. For a batch tool it also leaves the practical batch-size ceiling unstated, so an agent cannot fully predict the response.

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 description coverage is 0%, so the description must carry both parameters, and it does: 'names' is shown to accept 'Last, First' or 'First Last' (with 'Batch' implying the list form), and 'refresh=True' is defined as an immediate refetch. It does not spell out the array-vs-single-string relationship that the schema's anyOf allows.

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?

Names a specific verb and resource: a batch lookup of Rate My Professors ratings, with the accepted name formats stated up front. That is clearly distinguishable from the course-planning siblings (unw_course, unw_search, unw_remaining), though the description never explicitly routes against them.

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 'Batch' and by the cache/refresh note, which tells an agent that repeat calls are cheap and that refresh is for forcing fresh data. There is no explicit statement of when to prefer this over another tool or when a lookup is inappropriate.

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