Linux MCP Server

Get network interfaces

get_network_interfaces

Read-only

Retrieve IP addresses, traffic statistics, and configuration details for network interfaces on local or remote Linux hosts to diagnose connectivity and performance issues.

Instructions

Get detailed information about network interfaces including address and traffic statistics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`host`	Yes	System to run on: 'localhost' for the system the MCP server runs on, or a remote host to connect to via SSH

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.7.0Oct 3, 2026

removedInput schema / properties / host / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / host / default
```
Removed value: -null
```

changedInput schema / properties / host / description

Previous value: -"Remote host to connect to via SSH"New value: +"System to run on: 'localhost' for the system the MCP server runs on, or a remote host to connect to via SSH"

addedInput schema / properties / host / examples

Added value: +[
+  "localhost",
+  "web1.example.com"
+]

addedInput schema / properties / host / type
```
Added value: +"string"
```
addedInput schema / required
```
Added value: +[
+  "host"
+]
```

Changed1 schema field changedv1.6.0Sep 4, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv0.1.0Mar 11, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's burden is light. It adds useful content context (address and traffic statistics), but says nothing about SSH auth requirements for the remote-host path or whether the call can be slow or partial on unreachable hosts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence that leads with the action and immediately names the returned data. Nothing redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail need not be in the description, and the single parameter is fully documented. For a simple read-only tool this is nearly sufficient; only the remote-host connection behavior is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single 'host' parameter and the schema documents it at 100% coverage, including the localhost-vs-SSH semantics and examples. The description adds nothing beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (network interfaces) and names the payload (addresses, traffic statistics), so the agent knows exactly what comes back. It does not explicitly contrast itself with the adjacent siblings get_network_connections and get_listening_ports, so the distinction must be inferred from the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use context, no prerequisites, and does not mention the closely related get_network_connections or get_listening_ports siblings an agent could confuse it with. Usage is only implied by the resource name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.