Simple MCP 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 |
|---|---|
| read_fileB | 指定されたファイルの内容を読み込みます（許可されたディレクトリのみ） |
| write_fileC | 指定されたファイルにテキストを書き込みます（許可されたディレクトリのみ） |
| list_directoryB | 指定されたディレクトリの内容を一覧表示します（許可されたディレクトリのみ） |
| get_system_infoB | システム情報を取得します |
| create_sample_fileB | サンプルファイルを作成します（テスト用） |
| get_allowed_pathsB | アクセス可能なパスの一覧を表示します |
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: create_sample_file is for generating test files, get_allowed_paths lists accessible directories, get_system_info retrieves system metadata, list_directory shows directory contents, read_file reads file content, and write_file writes to files. There is no overlap in functionality, making tool selection straightforward.
All tool names follow a consistent verb_noun pattern using snake_case: create_sample_file, get_allowed_paths, get_system_info, list_directory, read_file, and write_file. This uniformity enhances readability and predictability across the tool set.
With 6 tools, the server is well-scoped for file and system operations, covering creation, reading, writing, listing, and information retrieval. Each tool serves a distinct role without redundancy, making the count appropriate for the domain.
The tool set provides strong coverage for basic file operations and system queries, including create, read, write, list, and info retrieval. A minor gap exists in update or delete operations for files, but agents can work around this using write_file for updates, and the domain is reasonably complete for a simple server.