UniFi Internal API MCP Server

stat_authorizations

Fetch authorization records for a specified time range, defaulting to the past 7 days. Use start and end Unix timestamps to filter results.

Instructions

Fetch authorization records. Defaults to past 7 days.

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

Input Schema

Name	Required	Description	Default
`end`	No	End Unix timestamp (seconds)
`start`	No	Start Unix timestamp (seconds)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the default behavior of returning records from the past 7 days, which is useful. However, it omits other behavioral aspects like pagination, ordering, or whether the records are filtered by anything else, so it provides minimal but non-zero transparency.

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 action, and contains no extraneous information. Every word earns its place.

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?

The tool is simple with only two optional parameters and an output schema, which explains return values. The description covers the core purpose and default behavior, making it adequate for most uses. However, it lacks usage context or exclusions, which is a minor gap given the available sibling complexity.

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 coverage is 100% for the two optional parameters 'start' and 'end', so the baseline is 3. The description adds a small semantic note about the default time range (past 7 days), which clarifies how the default null values are interpreted, but it doesn't provide additional per-parameter detail beyond the schema.

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?

The description clearly states 'Fetch authorization records' with a specific verb and resource, which distinguishes it from sibling tools like stat_sessions or list_clients. However, it doesn't elaborate on what exactly constitutes 'authorization records,' so it's clear but not maximally distinguishing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description only mentions the default time range ('Defaults to past 7 days'), which is behavioral rather than usage context. There are no explicit when/when-not conditions or alternative tool names.

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

Deploy Server