UniFi Internal API MCP Server

stat_ips_events

Retrieve Intrusion Prevention and Detection (IPS/IDS) events from UniFi to analyze security incidents. Optionally set a custom time range and limit, defaulting to the past 24 hours.

Instructions

Fetch IPS/IDS events. 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_ips_events"
  }
}

Input Schema

Name	Required	Description
`end`	No	End timestamp in ms
`limit`	No	Maximum events to return
`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

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'Fetch' implies a read-only operation, and the 24-hour default behavior is useful. However, it does not disclose potential volume handling, ordering, or whether events are raw or aggregated, leaving some gaps.

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?

Two concise sentences with no wasted words. Every piece of information is directly relevant: the action and the default time scope.

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

Completeness3/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 3 optional parameters and an output schema, so a minimal description can be adequate. However, the ambiguity between this and sibling tools like list_events is not resolved, and the default limit behavior is left to the schema. The description is adequate but not fully 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 input schema already documents all parameters with 100% coverage. The description adds the semantic that null start/end means the past 24 hours, which is a small but useful addition beyond the schema. This meets the baseline of 3.

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 uses the specific verb 'Fetch' and clearly identifies the resource as 'IPS/IDS events', which is distinct from sibling tools like list_events or list_alarms. However, it does not explicitly contrast it with those siblings, so it falls just short of a 5.

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 states a default time window ('Defaults to past 24 hours'), which is a usage hint, but it provides no guidance on when to choose this tool over alternatives, no exclusions, and no mention of conditions that might require different tools.

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

Deploy Server