netdiag-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 |
|---|---|
| diagnoseB | Run the full bottom-up diagnosis against a site and say which layer fails and how to fix it. Args: target: Host name or IP address the user is trying to reach, e.g. youtube.com. port: TCP port of the service, 443 for websites. |
| interfacesA | List network interfaces: up or down, IPv4/IPv6 addresses, MAC, speed and error counters (physical and data link layers). |
| wifi_signalA | Wi-Fi signal strength in dBm and a strong/ok/weak rating, if the computer is on Wi-Fi. |
| ip_configA | This computer's IPv4 addresses, default gateway and DNS servers, like |
| pingA | Ping a host: replies, packet loss, average latency and jitter. Args: host: Host name or IP address. count: Number of echo requests, 1 to 10. |
| tracerouteB | List every router on the path to a host and where the replies stop. Args: host: Host name or IP address. max_hops: Most routers to try, 1 to 30. |
| dns_lookupA | Resolve a name to IP addresses with the system's DNS, or with a given DNS server such as 1.1.1.1. Args: name: Host name to look up, e.g. youtube.com. server: Optional DNS server IP to ask instead of the system's own. |
| port_checkA | Try a TCP three-way handshake to host:port and report open, refused or timed out. Args: host: Host name or IP address. port: TCP port, e.g. 443 for HTTPS, 80 for HTTP, 53 for DNS. |
| http_checkA | Request a web page's headers and report the HTTP status code and response time. Args: url: Address such as https://youtube.com; https is assumed if no scheme is given. |
| route_tableC | The computer's routing table, including the default route (0.0.0.0/0). |
| arp_tableC | IP-to-MAC address pairs this computer has learned on the local network. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct diagnostic layer or probe (interface listing, Wi-Fi, IP config, routing, ARP, DNS, ping, traceroute, port, HTTP), so boundaries are mostly crisp. The only mild overlap is the aggregate `diagnose` versus the individual probes it presumably invokes, but its 'identify failing layer and fix' framing distinguishes it.
Most names follow a noun_noun or noun-phrase convention (wifi_signal, ip_config, dns_lookup, port_check, http_check, route_table, arp_table) with `interfaces` as a plain noun. `diagnose`, `ping`, and `traceroute` are verb/vague outliers, but they are conventional names for these utilities and remain readable.
Eleven tools is well within the ideal 3-15 range and each covers a distinct layer or probe in a bottom-up network diagnosis workflow. Nothing feels redundant or missing at the count level.
The surface covers physical/data-link (interfaces, wifi_signal), network (ip_config, route_table, arp_table), transport (ping, traceroute, port_check), and application (dns_lookup, http_check) layers, plus an aggregate `diagnose`. Minor gaps exist—no active connection listing (netstat-equivalent), DHCP/lease info, or bandwidth/MTU test—but core diagnostic workflows are covered.