Skip to main content
Glama
Sign In
unifi-mcp-server

unifi-mcp-server

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wan-uptime-trend

Read-only

Aggregate WAN uptime across sites, flagging connections below a configurable threshold (default 95%) and sorting by lowest uptime for quick identification of problematic WANs.

Instructions

Aggregate WAN uptime across all sites with severity flagging (default threshold 95%). Returns per-WAN sorted by lowest uptime first.

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": "wan-uptime-trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNoUptime % threshold below which WAN is flagged (default: 95)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.4
  2. Removedv1.12.3
  3. First observedv1.11.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by specifying sorting order (lowest uptime first), severity flagging, and default threshold. No contradictions with annotations.

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?

The description is two sentences long, front-loaded with the main purpose, and every sentence adds unique information (aggregation, flagging, sorting). No wasted words.

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 simple tool with one optional parameter and no output schema, the description covers the key aspects: what it does, the flagging behavior, and sorting. It lacks detail on output structure, but given the simplicity, it is reasonably complete.

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?

The schema description for 'threshold' already explains its purpose and default (95%). The description merely restates this information without adding further semantics. With 100% schema coverage, baseline 3 is appropriate.

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 uses a specific verb 'aggregate' and resource 'WAN uptime across all sites', details severity flagging with a default threshold, and states the sorting order. This clearly distinguishes the tool from sibling tools like 'get-isp-metrics' or 'list-sites'.

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?

The description implies the tool is for getting a global WAN uptime overview with flagging, but it does not explicitly state when to use it versus alternatives (e.g., per-site tools) or when not to use it. Usage guidance is only implied.

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