openEuler MCP Toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENEULER_MCP_ALLOWED_ROOTS | No | Allowed directories for file access, separated by system path separator (e.g., ':'). Default is the server's startup directory. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_memory_infoA | Read current system RAM, swap, and Linux /proc/meminfo values. |
| get_process_memoryA | Read RSS, VMS, and the largest memory mappings for one process. |
| sample_memory_trendC | Sample system memory usage and classify its short-term direction. |
| simulate_page_replacementC | Simulate FIFO, LRU, CLOCK, or optimal page replacement. |
| get_filesystem_infoB | Read mounted filesystems, space usage, and inode counts when available. |
| analyze_file_distributionC | Summarize file counts, sizes, extensions, and largest paths in a directory. |
| monitor_file_metadataB | Poll file size and timestamps; this is metadata polling, not access tracing. |
| simulate_disk_allocationB | Simulate transactional contiguous, linked, or indexed block allocation. |
| get_process_treeB | Read a bounded parent-child process tree from a selected root PID. |
| monitor_context_switchesB | Sample system-wide or per-process context-switch deltas. |
| simulate_cpu_schedulingC | Simulate CPU scheduling and report waiting, turnaround, and response metrics. |
| sample_cpu_time_ratiosB | Sample CPU time deltas and normalize them into per-state ratios. |
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 12 tools
Tools cover distinct areas like memory, filesystem, processes, and CPU scheduling, but some memory-related tools (get_memory_info, sample_memory_trend, get_process_memory) could be confused. Overall, each tool has a specific purpose with limited overlap.
Names use mixed verb patterns (get_, monitor_, sample_, simulate_, analyze_) rather than a consistent verb_noun structure. While readable, the lack of pattern may cause hesitation in selecting the correct tool.
With 12 tools, the count falls well within the ideal 3-15 range for a system toolkit. Each tool serves a clear function without unnecessary bloat or sparseness.
The toolkit covers memory, filesystem, process, and CPU scheduling domains, but lacks basic tools like listing all processes, CPU info, or network stats. Notable gaps exist for a comprehensive system toolkit.