Skip to main content
Glama

Get speed test history

unifi_get_speedtest_results
Read-only

Retrieve gateway WAN speed test results, including time, download/upload Mbps, latency, and test server, to review recent network performance.

Instructions

List the gateway's WAN speed test results, newest first (default last 168 hours): time, download and upload in Mbps, latency in ms and test server.

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

Input Schema

NameRequiredDescriptionDefault
siteNoSite name/ID as used in the API (e.g. 'default'). Defaults to the configured site. See unifi_list_sites.
hoursNoLook back this many hours (default 168)
limitNoMaximum items to return (default 100)
fieldsNoOnly return these fields per item (dot paths, e.g. uplink.name)
searchNoCase-insensitive substring match on names, MACs, IPs and similar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / fields / description
      Added value: +"Only return these fields per item (dot paths, e.g. uplink.name)"
    • changedInput schema / properties / limit / description
      Previous value: -"Default 100"New value: +"Maximum items to return (default 100)"
    • addedInput schema / properties / search / description
      Added value: +"Case-insensitive substring match on names, MACs, IPs and similar"
  2. First observedv0.8.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint=true, openWorldHint=false), so the description's added value is the ordering ('newest first'), the default look-back window, and the units of each measurement — all facts an agent cannot get from the annotation set. It stops short of explaining the odd idempotentHint=false (results change as new tests run) or how limit interacts with the time window.

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?

A single front-loaded sentence with the resource, the ordering and the default window stated before the field list. Every clause carries information; there is no filler.

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?

With no output schema, the description usefully enumerates the return fields so the agent knows the shape of a result, and it discloses ordering and the default time window for a five-parameter but fully documented tool. The only gap is that it never hints that limit defaults to 100 and can truncate long histories.

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 site, hours, limit, fields and search are fully documented in the schema; the description only restates the 168-hour default for hours. Baseline 3 applies since the schema carries the burden and the description adds nothing about the remaining four parameters.

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?

States a specific verb and resource ('List the gateway's WAN speed test results') and even enumerates the returned measurements (time, download/upload Mbps, latency ms, server). It is clearly distinct from every listed sibling, none of which touch speed tests, though it never explicitly disambiguates itself from anything.

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 default 168-hour window implies the intended 'recent history' usage, but there is no explicit when-to-use guidance, no mention of what to do if no tests exist, and no routing to an alternative tool for related questions (e.g. site health or traffic reports).

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