Base64 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 |
|---|---|
| base64_encode_textA | 将文本转换为Base64编码 |
| base64_decode_textA | 将Base64编码解码为文本 |
| base64_encode_imageA | 将图片转换为Base64编码 |
| base64_decode_imageA | 将Base64编码解码为图片 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| base64_usage_guide | 提供Base64服务的基本使用指南 |
| encode_text_prompt | 文本编码提示模板 |
| encode_image_prompt | 图片编码提示模板 |
| error_handling_prompt | 错误处理提示模板 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Every tool has a clearly distinct purpose with no ambiguity. The four tools cleanly separate into two decode operations (image vs text) and two encode operations (image vs text), each targeting specific data types and use cases. An agent can easily distinguish between them based on the input/output type and operation direction.
All tools follow a perfectly consistent verb_noun pattern with 'base64_' prefix, then operation (encode/decode), then target type (image/text). The naming is predictable, readable, and follows the same convention throughout without any deviations or mixed styles.
Four tools is ideal for this server's purpose. It provides complete coverage of the Base64 domain with exactly the right granularity: encode and decode operations for both text and image data types. No tool feels redundant or missing, and the count is well-scoped for the functionality offered.
The tool surface is complete for Base64 operations. It covers both encoding and decoding for the two primary data types (text and images) that Base64 typically handles. There are no gaps in the CRUD/lifecycle for this domain, and agents can perform all expected Base64 transformations without workarounds.