Skip to main content
Glama

Get controller system info

unifi_get_system_info
Read-only

Retrieve UniFi controller system details—Network application version, hostname, timezone, uptime, and update availability—to verify controller health and plan updates.

Instructions

Get the controller's own details (stat/sysinfo): Network application version, hostname, timezone, uptime and whether an application update is available. To check application and device firmware updates together use unifi_check_updates. For each device's firmware use unifi_get_firmware_status.

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

Input Schema

NameRequiredDescriptionDefault
siteNoSite name/ID as used in the API (e.g. 'default'). Defaults to the configured site. See unifi_list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the shape of the returned details, but says nothing about auth/permission requirements or any cost of calling it; the idempotentHint=false on a read-only info call is also left unexplained.

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?

Three short sentences, front-loaded with the core purpose before the two routing sentences. Every sentence earns its place with no filler or repetition of the title.

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 read-only, single-optional-parameter info tool with full schema coverage and safety annotations, the description covers purpose, return contents, and sibling routing adequately. Minor room remains on operational context such as permissions, but nothing essential for correct invocation is missing.

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 description coverage is 100% and the single optional 'site' parameter is fully documented in the schema, including the pointer to unifi_list_sites. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the controller's own details') and enumerates the returned fields (version, hostname, timezone, uptime, update availability). It explicitly distinguishes itself from unifi_check_updates and unifi_get_firmware_status, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Names two alternatives together with the exact condition that selects each: combined app+device update checks go to unifi_check_updates, per-device firmware goes to unifi_get_firmware_status. That leaves no ambiguity about when this tool is the right one.

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