portviewer
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_allA | 列出所有 IPv4 / IPv6 TCP + UDP 网络连接。 |
| list_tcpB | 列出 TCP IPv4 + IPv6。 |
| list_tcp4C | 列出 IPv4 TCP。 |
| list_tcp6C | 列出 IPv6 TCP。 |
| list_udpB | 列出 UDP IPv4 + IPv6。 |
| list_udp4C | 列出 IPv4 UDP。 |
| list_udp6C | 列出 IPv6 UDP。 |
| get_listening_portsB | 获取所有 TCP LISTEN 端口。 |
| get_established_connectionsB | 获取所有 TCP ESTABLISHED 连接。 |
| is_port_usedB | 判断本地端口是否出现在系统网络连接表中。 |
| is_tcp_port_usedC | 判断 TCP 端口是否被使用。 |
| is_udp_port_usedC | 判断 UDP 端口是否被使用。 |
| is_tcp_port_listeningC | 判断 TCP 端口是否存在 LISTEN 状态。 |
| find_portC | 查询使用指定本地端口的所有记录。 |
| find_tcp_portC | 查询使用指定本地 TCP 端口的所有记录。 |
| find_udp_portB | 查询使用指定本地 UDP 端口的所有记录。 |
| find_listening_portC | 查询指定 TCP LISTEN 端口。 |
| find_endpointD | 查询指定 IP + Port。 |
| kill_processC | 结束指定 PID 的进程。 |
| get_process_treeC | 返回指定进程所处的完整进程树。 |
| kill_process_treeC | 结束指定 PID 及其子孙进程。 |
| get_process_portsB | 获取某个进程正在使用的全部 TCP / UDP 端口。 |
| get_process_tcp_portsC | 获取某个进程使用的 TCP 连接。 |
| get_process_udp_portsC | 获取某个进程使用的 UDP 连接。 |
| get_port_processesC | 获取使用指定端口的所有进程。 |
| get_port_processC | 获取指定端口的第一个进程。 |
| can_bind_tcpC | 实际尝试 bind TCP 端口。 |
| can_bind_udpC | 实际尝试 bind UDP 端口。 |
| get_free_portC | 返回指定范围内任意一个空闲端口。 |
| get_free_portsC | 返回指定范围内所有空闲端口。 |
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 30 tools
Many tools overlap heavily: list_tcp/list_tcp4/list_tcp6 and list_udp/list_udp4/list_udp6, is_port_used/is_tcp_port_used/is_udp_port_used, and find_port/find_tcp_port/find_udp_port/find_listening_port. The descriptions clarify the granularity, but an agent must carefully distinguish near-duplicate variants.
All tool names use consistent snake_case and generally follow a verb_noun pattern (list_tcp, get_listening_ports, find_endpoint, kill_process, can_bind_udp). Minor singular/plural pairs like get_port_process/get_port_processes are predictable and intentional.
30 tools is excessive for a port/process viewer, largely because many operations are expanded into protocol- and IP-version-specific permutations. This creates redundancy rather than distinct capability, making the surface heavy for the domain.
The tool set comprehensively covers listing, filtering, checking, finding, binding, free-port discovery, process inspection, process tree retrieval, and process termination for TCP/UDP and IPv4/IPv6. No obvious lifecycle or inspection operation for the stated port/process domain is missing.