Skip to main content
Glama

blob_container_list

Lists all Blob Storage containers in Azure to manage storage resources and audit container inventory.

Instructions

List all Blob Storage containers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic for the 'blob_container_list' tool: retrieves all blob containers using BlobServiceClient.list_containers() and extracts their names into a response dictionary.
    elif name == "blob_container_list":
        containers = blob_service_client.list_containers()
        container_names = [container.name for container in containers]
        response = {"container_names": container_names}
  • Pydantic schema definition for the 'blob_container_list' tool, specifying no required input parameters.
    Tool(
        name="blob_container_list",
        description="List all Blob Storage containers",
        inputSchema={"type": "object", "properties": {}},
    ),
  • Tool registration via the list_tools handler, which returns get_azure_tools() including 'blob_container_list'.
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        """List available Azure tools"""
        logger.debug("Handling list_tools request")
        return get_azure_tools()  # Use get_azure_tools
  • Dispatch logic in call_tool handler that routes 'blob_container_list' (blob_ prefixed tools) to the blob storage operations handler.
    if name.startswith("blob_"):  # Updated prefix to blob_
        return await handle_blob_storage_operations(
            azure_rm, name, arguments
        )  # Use blob handler
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description doesn't address whether this requires specific permissions, returns paginated results, includes metadata, or has rate limits. For a listing tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 that states the core functionality without any wasted words. It's front-loaded with the essential action and resource, making it immediately scannable and appropriately sized for a simple listing tool.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more behavioral context (e.g., what the list returns, any limitations). The description covers the basic purpose but leaves the agent to assume details about the operation's behavior and results.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate since there are no parameters to describe. The baseline for 0 parameters with full schema coverage is 4, as no additional parameter semantics are needed.

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 clearly states the verb ('List') and resource ('all Blob Storage containers'), making the purpose immediately understandable. It distinguishes from siblings like blob_container_create and blob_container_delete by specifying a read-only listing operation. However, it doesn't explicitly differentiate from blob_list (which lists blobs within containers) or cosmosdb_container_list (which lists CosmosDB containers).

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. It doesn't mention when to use blob_container_list versus blob_list (for listing blobs within containers) or cosmosdb_container_list (for CosmosDB containers). There are no prerequisites, exclusions, or explicit alternatives named, leaving the agent to infer usage from context 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/mashriram/azure_mcp_server'

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