Linux MCP Server

Get memory information

get_memory_information

Read-only

Retrieve detailed physical and swap memory usage from a local or SSH-connected Linux host to diagnose memory pressure and capacity issues.

Instructions

Get detailed memory including physical and swap.

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
`ram`	Yes	Parsed memory information from free command.
`swap`	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"
+]
```

Changed8 schema fields changedv1.6.0Sep 4, 2026

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

removedOutput schema / $defs

Removed value: -{
-  "MemoryInfo": {
-    "description": "Parsed memory information from free command.",
-    "properties": {
-      "available": {
-        "default": 0,
-        "type": "integer"
-      },
-      "buffers": {
-        "default": 0,
-        "type": "integer"
-      },
-      "cached": {
-        "default": 0,
-        "type": "integer"
-      },
-      "free": {
-        "type": "integer"
-      },
-      "shared": {
-        "default": 0,
-        "type": "integer"
-      },
-      "total": {
-        "type": "integer"
-      },
-      "used": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "total",
-      "used",
-      "free"
-    ],
-    "type": "object"
-  },
-  "SwapInfo": {
-    "description": "Parsed swap information from free command.",
-    "properties": {
-      "free": {
-        "type": "integer"
-      },
-      "total": {
-        "type": "integer"
-      },
-      "used": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "total",
-      "used",
-      "free"
-    ],
-    "type": "object"
-  }
-}

removedOutput schema / properties / ram / $ref
```
Removed value: -"#/$defs/MemoryInfo"
```

addedOutput schema / properties / ram / description

Added value: +"Parsed memory information from free command."

addedOutput schema / properties / ram / properties

Added value: +{
+  "available": {
+    "default": 0,
+    "type": "integer"
+  },
+  "buffers": {
+    "default": 0,
+    "type": "integer"
+  },
+  "cached": {
+    "default": 0,
+    "type": "integer"
+  },
+  "free": {
+    "type": "integer"
+  },
+  "shared": {
+    "default": 0,
+    "type": "integer"
+  },
+  "total": {
+    "type": "integer"
+  },
+  "used": {
+    "type": "integer"
+  }
+}

addedOutput schema / properties / ram / required

Added value: +[
+  "total",
+  "used",
+  "free"
+]

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

changedOutput schema / properties / swap / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/SwapInfo"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Parsed swap information from free command.",
+    "properties": {
+      "free": {
+        "type": "integer"
+      },
+      "total": {
+        "type": "integer"
+      },
+      "used": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "total",
+      "used",
+      "free"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv0.1.0Mar 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already establishes this as a safe read, and the description adds that the result covers both physical and swap memory, which is useful scope information. However, it says nothing about behavior for remote hosts over SSH, latency, or failure modes when a host is unreachable, so it adds only modest context beyond the annotations.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler, covering verb, resource, and content scope. It is efficient, though extremely terse given it is the entire description.

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, the description need not explain return values, and the sole parameter is fully documented in the schema. What remains missing is only usage/alternative guidance, which is a minor gap for a simple read tool.

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 description coverage is 100%, and the host parameter is fully documented in the schema (localhost vs remote SSH host). The description adds no parameter-level meaning, 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+resource ('Get detailed memory') and scopes the content to physical and swap memory, which cleanly separates it from siblings like get_cpu_information and get_disk_usage. It does not name a sibling or explicitly rule out alternatives, but the resource is unambiguous.

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?

There is no explicit when-to-use guidance, no mention of when to prefer get_system_information or other resource tools, and no prerequisites stated. Usage is only implied by the tool name and the memory resource it targets.

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