Encoding 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 |
|---|---|
| create_empty_fileA | Create an empty file with specified encoding. Creates only an empty file so Agent can fill in content. |
| detect_file_encodingC | Accurately detect file encoding using professional libraries. |
| convert_file_encodingC | Convert file to specified encoding. Automatic backup support. |
| get_system_infoB | Check Encoding MCP system information. Shows available libraries and supported encodings. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: convert_file_encoding handles file conversion, create_empty_file creates new files, detect_file_encoding identifies encodings, and get_system_info provides system metadata. An agent can easily distinguish between these operations without confusion.
All tool names follow a consistent verb_noun pattern with snake_case: convert_file_encoding, create_empty_file, detect_file_encoding, and get_system_info. This predictable naming scheme makes the tool set easy to navigate and understand.
With 4 tools, the server is well-scoped for encoding operations, covering conversion, creation, detection, and system info. Each tool earns its place without redundancy, making the count appropriate for the domain's core functions.
The tool set covers key encoding workflows: detect, convert, create, and system info, with no dead ends. A minor gap exists in operations like deleting or renaming encoded files, but agents can work around this, and the core functionality is solid.