UniFi Internal API MCP Server

stat_speedtest_results

Fetch UniFi speed test results for a specified period. Defaults to the past 24 hours; supply start/end timestamps to adjust the range.

Instructions

Fetch speed test results. Defaults to past 24 hours.

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

Input Schema

Name	Required	Description	Default
`end`	No	End timestamp in ms
`start`	No	Start timestamp in ms

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the default time window, which is a behavioral trait, but does not mention whether the operation is read-only (though 'fetch' implies it), result ordering, or any potential rate limits. It is minimally transparent but lacks richer context.

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 short sentences with the action front-loaded. Every word earns its place—no filler, no redundancy.

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 low-complexity tool with two optional parameters and an output schema, the description covers the essential default behavior. It does not explain ordering or time zone handling, but these are not critical for a simple fetch, and the output schema likely covers return structure.

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?

The schema already describes both parameters (start/end timestamps) with 100% coverage. The description adds that omitting these parameters defaults to the past 24 hours, which clarifies behavior beyond the schema alone—valuable for an agent deciding whether to pass parameters.

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 clearly states a specific action on a specific resource: 'Fetch speed test results.' This is distinct from sibling tools like stat_sysinfo or stat_sessions, and the additional default time window provides useful scope.

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 gives context that the tool defaults to past 24 hours, implying typical use for recent data, but it does not explicitly mention when to use this versus alternatives or provide exclusions. With no overlapping siblings, usage is implied rather than explicitly guided.

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

Deploy Server