UniFi Internal API MCP Server

stat_sessions

Retrieve UniFi login sessions with optional filters for date range, client MAC, and session type. Defaults to past 7 days.

Instructions

Fetch login sessions. 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_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No	End Unix timestamp (seconds)
`mac`	No	Client MAC to filter by
`start`	No	Start Unix timestamp (seconds)
`session_type`	No	'all', 'guest', or 'user'	all

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must carry the behavioral burden. It discloses the default 7-day window but does not mention whether the operation is read-only, what permissions are needed, or any rate limits or output shape beyond the schema. This is minimal for a tool with no annotation support.

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, front-loaded with the primary action and followed by a key default. There is no redundant wording or filler, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description lacks usage context, alternative tool comparisons, and behavioral traits. For a tool with four parameters and many siblings, this minimal description is insufficient for an agent to reliably select it among close alternatives like stat_sta_sessions_latest.

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 100%, so parameters are fully documented in the schema. The description adds value by clarifying that null start/end defaults to the past 7 days, which is not obvious from the schema's null defaults. This semantic enrichment goes beyond the structured data.

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 the verb and resource: 'Fetch login sessions.' This distinguishes it from other stat tools, though it does not explicitly contrast with stat_sta_sessions_latest. The additional default time range adds useful context.

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?

The description provides no guidance on when to use this tool vs. alternatives like stat_sta_sessions_latest or stat_authorizations. It only notes the default time range, which implies usage for historical sessions but offers no exclusions or comparisons.

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

Deploy Server