MCP Complete Implementation Guide
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 |
|---|---|
| read_fileC | Read the contents of a file |
| write_fileC | Write content to a file |
| list_directoryC | List the contents of a directory |
| get_system_infoC | Get system information |
| execute_commandB | Execute a system command (use with caution) |
| fetch_urlC | Fetch content from a URL |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: execute_command runs system commands, fetch_url retrieves web content, get_system_info provides system metadata, list_directory shows directory contents, read_file reads file data, and write_file writes file data. The descriptions make it impossible to confuse one tool for another.
All tools follow a consistent verb_noun pattern (e.g., execute_command, fetch_url, read_file) using snake_case throughout. There are no deviations in naming style or convention across the entire set.
With 6 tools, this is well-scoped for a system utility server. Each tool earns its place by covering distinct, fundamental operations like file I/O, system commands, and network requests, without being overly sparse or bloated.
The toolset covers core system and file operations comprehensively, including read/write, directory listing, command execution, and URL fetching. A minor gap exists in lacking update/delete file operations, but agents can work around this using existing tools like write_file for overwrites.