Linux MCP Server

Get system information

get_system_information

Read-only

Retrieve Linux host details including OS, distribution, kernel, uptime, last boot, PCP install/service status, and historical PCP ranges from localhost or remote SSH hosts for diagnostics.

Instructions

Get basic system information, including operating system, distribution, kernel version, uptime, last boot time, PCP installation and service status, and historical PCP time ranges.

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
`pcp`	No	PCP availability and service status.
`arch`	No
`kernel`	No
`uptime`	No
`os_name`	No
`hostname`	No
`boot_time`	No
`os_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

addedOutput schema / properties / pcp

Added value: +{
+  "description": "PCP availability and service status.",
+  "properties": {
+    "available_time_ranges": {
+      "anyOf": [
+        {
+          "items": {
+            "description": "Available time ranges for PCP historical data.",
+            "properties": {
+              "end": {
+                "format": "date-time",
+                "type": "string"
+              },
+              "start": {
+                "format": "date-time",
+                "type": "string"
+              }
+            },
+            "required": [
+              "start",
+              "end"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "installed": {
+      "default": false,
+      "type": "boolean"
+    },
+    "metrics_guide": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "missing_commands": {
+      "description": "Required PCP commands that are not installed. On Fedora/RHEL, pmlogger is shipped by the 'pcp' package and pmrep by 'pcp-system-tools'.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pmcd_running": {
+      "default": false,
+      "type": "boolean"
+    },
+    "pmlogger_running": {
+      "default": false,
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv1.6.0Sep 4, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
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 establishes this is a safe, non-mutating call, so the bar is lower. The description does add genuine context by disclosing that PCP installation/service status and historical PCP time ranges are included, which the schema does not reveal. However, it says nothing about SSH connection behavior for remote hosts, latency, or permissions, so it is solid but not rich.

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 sentence that front-loads the core purpose ('Get basic system information') and then lists specifics. Every enumerated item is meaningful content, with no filler or redundancy.

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?

An output schema exists, so the description is not obligated to explain return values, and it is complete enough for an agent to call the tool correctly. The only mild gap is the absence of guidance on remote/SSH prerequisites and how this differs from the other system-information siblings.

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 parameter ('host') and schema description coverage is 100%, with the schema itself explaining 'localhost' vs a remote host over SSH and providing examples. The description adds no parameter-level meaning beyond that, 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?

The description gives a specific verb ('Get') plus a resource ('basic system information') and then enumerates the exact contents: OS, distribution, kernel version, uptime, last boot time, PCP install/service status, and historical PCP time ranges. This enumeration implicitly distinguishes it from narrower siblings like get_cpu_information and get_hardware_information, but it never names an alternative explicitly, so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. Usage is only implied by the enumerated contents — an agent can infer it is the general system-overview tool versus the specialized per-resource tools, but must make that inference itself.

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