Skip to main content
Glama

Check for updates

unifi_check_updates
Read-only

Check UniFi controller for available Network application updates, list devices needing firmware upgrades with current and available versions, and count up-to-date devices.

Instructions

Check for updates in one call: the latest Network application version the controller knows of (controller), the devices with a firmware upgrade (current and available version) and how many are up to date. For every 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_check_updates"
  }
}

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/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 structurally. The description adds genuinely useful behavioral detail by describing what the response is composed of (app version, upgradable devices, up-to-date count), but it says nothing about pagination, freshness of the version data, or what happens if the controller cannot reach the update service.

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 sentences, zero filler: the first front-loads the result contents and the second routes the agent to the correct sibling for per-device data. Nothing is repeated from the title or annotations.

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?

With no output schema, the description carries the burden of explaining return values and does so reasonably well by listing the three data groups. It is nearly complete for a one-optional-parameter read tool, with only minor gaps around freshness and error behavior.

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?

There is a single optional site parameter with 100% schema description coverage, and the description adds no additional meaning about it (format, default behavior, or effect on results). With the schema already doing the work, the baseline of 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?

The description uses a specific verb ("check for updates") and then enumerates exactly what the call returns: the latest Network application version known to the controller, devices with a firmware upgrade (with current and available version), and a count of up-to-date devices. It also names the sibling unifi_get_firmware_status as the tool for per-device firmware detail, so the agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Routing guidance is explicit in the closing sentence: for every device's firmware, use unifi_get_firmware_status instead. That names an alternative and the condition that selects it. It does not, however, state the broader when-to-use context (e.g. pre-upgrade triage vs. routine health checks), so it falls short of full when/when-not guidance.

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