MCP System Info Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sysinfoA | Get the current system information. Gives system information such as System, Node name, Release, Version, Machine, Processor CPU Information such as Processor, Physical Cores, Logical Cores Memory Information such as Total Memory, Available Memory, Used Memory, Memory Utilization Disk Information such as Total Disk Space, Used Disk Space, Free Disk Space, Disk Space Utilization |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_sysinfo' has a clear and distinct purpose of retrieving comprehensive system information, making it impossible for an agent to misselect among tools.
Since there is only one tool, it inherently follows a consistent naming pattern. The name 'get_sysinfo' uses a verb_noun format that is clear and predictable, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'MCP System Info Server', which suggests a broader scope for system information retrieval. While 'get_sysinfo' provides comprehensive data, the lack of additional tools (e.g., for specific components like CPU, memory, or disk details) makes the set feel thin and underdeveloped for the domain.
The tool 'get_sysinfo' covers a wide range of system information in one call, but the server's purpose implies potential for more granular operations. There are significant gaps, such as no tools for querying specific system metrics separately (e.g., get_cpu_info, get_memory_usage) or performing actions like monitoring changes, which limits agent flexibility and could lead to inefficiencies.