Skip to main content
Glama
jneless
by jneless

tos_list_buckets

List all available storage buckets in Volcengine TOS object storage service for bucket management and organization.

Instructions

列举 TOS 存储桶

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the tos_list_buckets tool. It calls tos_client.list_buckets() to retrieve all buckets and formats them as a JSON list with name, creation_date, and location.
    async def list_buckets(_args: Dict[str, Any]) -> List[TextContent]:
        """列举存储桶"""
        try:
            resp = tos_client.list_buckets()
            buckets = []
            for bucket in resp.buckets:
                buckets.append({
                    "name": bucket.name,
                    "creation_date": str(bucket.creation_date) if bucket.creation_date else None,
                    "location": bucket.location
                })
            return [TextContent(type="text", text=json.dumps(buckets, indent=2, ensure_ascii=False))]
        except Exception as e:
            return [TextContent(type="text", text=f"列举存储桶失败: {str(e)}")]
  • Tool registration in list_tools() function, defining the name, description, and input schema (empty properties) for tos_list_buckets.
    Tool(
        name="tos_list_buckets",
        description="列举 TOS 存储桶",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • Dispatch logic in call_tool() that routes the tos_list_buckets tool call to the list_buckets handler function.
    elif name == "tos_list_buckets":
        return await list_buckets(arguments)
  • Input schema for the tos_list_buckets tool, which requires no parameters (empty properties).
    inputSchema={
        "type": "object",
        "properties": {}
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('list') without any information about permissions required, rate limits, pagination, error conditions, or what the output looks like (e.g., bucket names, creation dates). This is inadequate for a tool that likely returns a list of resources.

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 phrase ('列举 TOS 存储桶') that directly conveys the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for its simplicity.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of bucket names or details), any behavioral traits like authentication needs or limitations, or how it fits with sibling tools. For a tool in a storage service context, this leaves significant gaps for an AI agent.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so the schema fully documents that no inputs are required. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since no parameters exist, and the description doesn't contradict or confuse this.

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 存储桶' (List TOS buckets) clearly states the verb ('list') and resource ('TOS buckets'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'tos_list_objects' which lists objects within buckets rather than the buckets themselves, preventing 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?

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention that this tool lists all buckets in the TOS service, while 'tos_list_objects' requires specifying a bucket to list its contents, or that 'tos_get_bucket_meta' retrieves metadata for a specific bucket. This lack of comparative context leaves usage unclear.

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