No user-submitted related servers found.
Scored across 117 tools
The tool set contains many overlapping and explicitly deprecated aliases that perform the same or nearly the same operation, such as getQosPolicy vs getQosPolicyRule/getQosMarkingRule/getDscpConfig, getApplicationAcl vs getAppControlRules, getDevice vs listDevices, and getClient vs listClients/getClientDetail. While some tools have distinct scopes, the volume of duplicate and near-duplicate endpoints makes misselection likely without reading full descriptions.
All names are camelCase and generally start with a verb such as get/list/search/diagnose, but the conventions are mixed: some use getXxx, some listXxx, and many use site-scoped prefixes like getSitesApsIpSetting or getSitesGatewaysGeneralConfig alongside device-scoped names like getApGeneralConfig. The pattern is readable but inconsistent enough that an agent cannot reliably predict whether a resource uses get, list, or a sites-prefixed form.
With 117 tools, the surface is far too large for an agent to navigate efficiently, especially because many are deprecated aliases, near-duplicates, or narrow single-field configuration getters. The count reflects endpoint-by-endpoint exposure rather than a well-scoped tool set.
The surface is almost entirely read-only get/list/diagnose operations and lacks obvious write/update/delete operations for configuration, which may be intentional for a 'safe' server but is a major capability gap. It also references missing actions such as triggerSpeedTest and triggerRfScan in descriptions, creating dead ends where the tool set cannot perform an instructed prerequisite.