Skip to main content
Glama
rhel-lightspeed

Linux MCP Server

by rhel-lightspeed
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Get disk usage

get_disk_usage
Read-only

Check disk space on Linux systems, revealing size, mount points, and utilization for local or remote hosts via SSH to diagnose storage issues.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoRemote host to connect to via SSH

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesystemsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv1.6.0
    • 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"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=true, and the description does not contradict this. It adds no additional behavioral details beyond the parameter mention of SSH, but this is adequate given the annotation coverage.

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?

The description is one concise sentence with no superfluous content, effectively conveying the tool's core function.

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?

While the output schema is not shown, the description gives hints about the returned data (size, mount points, utilization). It is sufficiently complete for this simple read operation.

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?

The single parameter 'host' has a description in the schema, and the tool description does not add further meaning. Schema coverage is 100%, so baseline is appropriate.

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

Purpose5/5

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

The description clearly states the tool retrieves disk space information including size, mount points, and utilization, which is specific and distinct from sibling tools like get_network_interfaces or get_process_info.

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?

No explicit when-to-use or alternative guidance is provided. The description only states what it does, not in which scenarios it should be preferred over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhel-lightspeed/linux-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server