Skip to main content
Glama
jneless
by jneless

tos_delete_bucket

Delete a TOS storage bucket to remove unused containers and manage cloud storage resources efficiently.

Instructions

删除 TOS 存储桶

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_nameYes存储桶名称

Implementation Reference

  • The main handler function that implements the tos_delete_bucket tool. It extracts the bucket_name from input arguments and calls tos_client.delete_bucket to perform the deletion, returning success or error message.
    async def delete_bucket(args: Dict[str, Any]) -> List[TextContent]:
        """删除存储桶"""
        bucket_name = args["bucket_name"]
        
        try:
            tos_client.delete_bucket(bucket_name)
            return [TextContent(type="text", text=f"成功删除存储桶: {bucket_name}")]
        except Exception as e:
            return [TextContent(type="text", text=f"删除存储桶失败: {str(e)}")]
  • The input schema definition for the tos_delete_bucket tool, specifying bucket_name as a required string parameter.
    inputSchema={
        "type": "object",
        "properties": {
            "bucket_name": {
                "type": "string",
                "description": "存储桶名称"
            }
        },
        "required": ["bucket_name"]
    }
  • Tool dispatch registration in the call_tool handler, mapping 'tos_delete_bucket' to the delete_bucket function.
    elif name == "tos_delete_bucket":
        return await delete_bucket(arguments)
  • Tool registration in list_tools, defining name, description, and schema for tos_delete_bucket.
    Tool(
        name="tos_delete_bucket",
        description="删除 TOS 存储桶",
        inputSchema={
            "type": "object",
            "properties": {
                "bucket_name": {
                    "type": "string",
                    "description": "存储桶名称"
                }
            },
            "required": ["bucket_name"]
        }
    ),
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose that deletion is destructive and irreversible, potential permissions required, error conditions (e.g., non-empty bucket), or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive deletion tool with no annotations and no output schema, the description is incomplete. It lacks critical context: what TOS is, the irreversible nature of deletion, prerequisites, and expected outcomes. This leaves significant gaps for safe agent operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with one parameter ('bucket_name') well-documented in the schema. The description adds no parameter-specific information beyond implying the bucket to delete. Baseline 3 is appropriate as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '删除 TOS 存储桶' clearly states the action (delete) and resource (TOS bucket). It distinguishes from siblings like 'tos_create_bucket' (create) and 'tos_delete_object' (delete object rather than bucket). However, it doesn't specify what TOS is or the scope of deletion, keeping it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., bucket must be empty), exclusions, or related tools like 'tos_list_buckets' for verification. The agent must infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jneless/tos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server