Catalyst Center client operations and monitoring - list/filter wired and wireless clients, detailed client lookup by MAC, client count analytics, time-based analysis, SSID and band filtering, wireless troubleshooting.
SkillScore68Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/16/2026
What it changes
Passed 13 of 19 test cases with the skill, and 8 of 19 without it.
Without skill41%
With skill68%
Checks it passed that the model alone missed
Calls get_api_compatible_time_range for each time window.
Uses get_clients_count with the wlc_name filter parameter.
Identifies health scores below 7 as indicating connection issues.
and 5 more in the full report
6 fixed9 passed either way7 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+384%
Agent turns
0%
Response time
-35%
Model gemini-3.6-flashMeasured 8/16/2026v115 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We want to check all clients connected to access switch ACC-SW-05 on Catalyst Center for the past 2 hours. Which parameter in the client list tool should be populated with the switch name?
What was checked, without and with the skill
Checked
Without skill
With skill
Populates connected_network_device_name with the target switch name.
Missed
Passed
case-14 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md467 linessingle file
Catalyst Center Client Operations and Monitoring
Catalyst Center MCP Server
All Catalyst Center tool calls use this invocation pattern:
Investigating specific client connectivity issues by MAC address
Capacity planning: how many clients per site, SSID, or band
Wireless troubleshooting: signal quality, RSSI, band steering analysis
Time-based analysis: client count trends over hours/days
Security investigations: locate a client by IP or MAC across the network
Help desk escalations: look up a user's device and connection details
SSID utilization and OS distribution analytics
Critical: Time Range Handling
The Catalyst Center client APIs require startTime and endTime in epoch milliseconds. The API enforces a 30-day maximum lookback for startTime.
ALWAYS call get_api_compatible_time_range FIRST to convert human-readable time ranges into valid epoch millisecond pairs before calling any client tool.