Linux MCP Server

Get disk usage

get_disk_usage

Read-only

Check disk space on local or remote RHEL-based Linux hosts via SSH, showing size, mount points, and utilization to diagnose storage issues.

Instructions

Get detailed disk space information including size, mount points, and utilization.

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
`filesystems`	No

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"
+]
```

Changed6 schema fields changedv1.6.0Sep 4, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / $defs

Removed value: -{
-  "FilesystemInfo": {
-    "description": "Individual filesystem entry from findmnt output.",
-    "properties": {
-      "avail": {
-        "default": "",
-        "type": "string"
-      },
-      "fstype": {
-        "default": "",
-        "type": "string"
-      },
-      "size": {
-        "default": "",
-        "type": "string"
-      },
-      "source": {
-        "default": "",
-        "type": "string"
-      },
-      "target": {
-        "default": "",
-        "type": "string"
-      },
-      "use%": {
-        "default": "",
-        "type": "string"
-      },
-      "used": {
-        "default": "",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-}

removedOutput schema / properties / filesystems / items / $ref
```
Removed value: -"#/$defs/FilesystemInfo"
```

addedOutput schema / properties / filesystems / items / description

Added value: +"Individual filesystem entry from findmnt output."

addedOutput schema / properties / filesystems / items / properties

Added value: +{
+  "avail": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "fstype": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "size": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "source": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "target": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "use%": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  },
+  "used": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": ""
+  }
+}

addedOutput schema / properties / filesystems / items / type
```
Added value: +"object"
```

First observedv0.1.0Mar 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read operation. The description adds what information is returned (size, mount points, utilization), which is useful context. It doesn't elaborate on remote SSH behavior or potential timeouts, but with annotations covering safety profile, a 3 is appropriate.

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?

A single, well-formed sentence that is front-loaded with the main purpose and efficiently lists the returned details. No wasted words.

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?

Given the presence of an output schema (which likely details return values) and a 100% coverage schema for parameters, the description is nearly complete for an agent to understand the tool's purpose and invocation. It could benefit from a note on remote host handling or timeouts, but those are minor given the structured fields.

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?

Schema coverage is 100%, so the single parameter 'host' is fully documented in the schema, including examples and the distinction between localhost and remote SSH. The description adds no parameter details beyond what the schema provides. Baseline 3 is correct when schema does the heavy lifting.

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 ('disk space information') with the fields returned (size, mount points, utilization). It is clearly distinguishable from siblings like get_memory_information or get_cpu_information, though it doesn't explicitly call out that differentiation.

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

Usage Guidelines3/5

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

Usage is implied by the tool's purpose (retrieving disk space info), but there is no explicit guidance on when to use this vs alternatives, nor any mention of prerequisites or exclusions. Adequate but with a clear gap.

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