mcp-system-info
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hardware_infoA | Get complete hardware information (CPU, memory, storage, graphics, battery, serial numbers) |
| get_system_statusA | Get system status information (operating system, network interfaces, CPU and memory usage) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Each tool targets a distinct aspect of system information: hardware details vs. dynamic system status. There is no overlap in purpose.
Both tools follow a consistent 'get_<domain>' pattern, making the naming predictable and clear.
With only 2 tools, the server feels minimal but not unreasonable for a focused purpose. However, the scope might benefit from a few more to cover software/process information.
The tools cover fundamental hardware and system status, but lack coverage of software inventory, running processes, or detailed storage analysis. The surface is functional but not comprehensive.