NetOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_pingB | Pings an IP address or hostname to check reachability, average latency, and packet loss. |
| get_gateway_telemetryB | Discover the local default gateway and check first-hop reachability. |
| get_wifi_telemetryA | Gathers local WiFi interface telemetry such as SSID, signal strength percentage, radio type, and link rates. |
| resolve_dnsA | Resolves a hostname using the local system resolver & measures resolution latency |
| create_incident_ticketC | Creates a structured operational incident ticket payload for escalation |
| query_incident_historyA | Queries past incident tickets to identify recurring failures, historical context, or open issues |
| lookup_remediationA | Look up specific remediation advice and thresholds from the triage runbook. Valid categories: 'physical' (or 'signal', 'L1'), 'packet_loss' (or 'loss'), 'latency' (or 'RTT', 'bufferbload'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_network | Guides the agent through a disciplined, bottom-up Layer 1-3 network diagnostic sequence |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_network_triage_runbook | Exposes standard-backed network triage guidelines as a runbook resource. |
TDQS
Scored across 7 tools
Each tool targets a distinct diagnostic or operational action: gateway telemetry, WiFi telemetry, ping, DNS, runbook lookup, and incident creation/history. The only possible overlap is reachability checks between get_gateway_telemetry and run_ping, but their scopes are explicitly separated by first-hop vs arbitrary target.
All tools follow a verb_noun snake_case pattern such as get_*, run_*, resolve_*, create_*, query_*, and lookup_*. There is no mix of casing or grammatical styles, and each verb clearly signals the tool's intended action.
Seven tools is a focused, appropriately scoped set for a NetOps assistant: four network diagnostics, one remediation reference, and two incident-management tools. Each tool adds a distinct capability without unnecessary bloat.
The set covers the core diagnostic loop with gateway/WiFi/ping/DNS checks, remediation lookup, and incident creation/history. It lacks some obvious extras like traceroute or incident update/close, but these are workable gaps rather than blocking omissions.