TOS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOS_BUCKETS | No | 指定访问的 TOS 桶,可选 | |
| TOS_ENDPOINT | Yes | 火山引擎 TOS Endpoint | |
| SECURITY_TOKEN | No | 火山引擎 Security Token,可选 | |
| VOLCENGINE_REGION | Yes | 火山引擎 TOS region | |
| VOLCENGINE_ACCESS_KEY | Yes | 火山引擎账号 ACCESS KEY | |
| VOLCENGINE_SECRET_KEY | Yes | 火山引擎账号 SECRET KEY |
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 |
|---|---|
| list_bucketsC | |
| list_objectsC | |
| get_objectB | |
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 3 tools
Each tool has a clearly distinct purpose with no ambiguity. get_object retrieves specific object content, list_buckets enumerates available buckets, and list_objects lists objects within a bucket. The three tools cover different operations without overlap.
All tool names follow a consistent verb_noun pattern with snake_case formatting. get_object, list_buckets, and list_objects maintain perfect naming consistency throughout the toolset.
With only 3 tools, this feels thin for a storage service interface. While the tools cover basic read operations, the absence of create, update, or delete operations makes this feel incomplete rather than minimal. The count is borderline for the apparent scope.
Significant gaps exist in this TOS storage interface. While it provides read operations (get_object, list_buckets, list_objects), it lacks essential CRUD operations like create_bucket, put_object, delete_object, or delete_bucket. Agents will encounter dead ends when trying to perform basic storage workflows.