UnifiyMe

get_events

Retrieve recent network events from UniFi to monitor activity and troubleshoot issues. Specify hours to look back.

Instructions

Get recent network events

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

Input Schema

Name	Required	Description	Default
`hours`	No	Number of hours to look back (default: 24)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but only states 'Get recent network events.' It does not clarify whether this is read-only, what kinds of events are returned, how results are ordered, or any limits like pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is compact and front-loaded, with no filler. It sacrifices explanatory value for brevity, but as a structure it is appropriately short for a one-parameter read operation.

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?

For a simple tool with no output schema, this might be acceptable if 'network events' were unambiguous. However, the large sibling set contains several event-like tools, and the description does not define event scope or distinguish itself, leaving the agent to guess.

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 covers 100% of the parameter, including the meaning and default of 'hours.' The description's word 'recent' weakly echoes the parameter's purpose but adds no meaningful semantic detail beyond the schema entry.

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 names a concrete action and resource: retrieving recent network events. It is clear at a basic level, but does not differentiate events from closely related siblings like get_alarms or get_router_logs, so it stops 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 gives no guidance on when to choose this tool over alternatives such as get_alarms, get_router_logs, or get_client_history. An agent must infer usage from the name and one optional parameter.

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

Deploy Server