Skip to main content
Glama
mashriram

Azure MCP Server

by mashriram
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

blob_delete

Remove specific files from Azure Blob Storage containers to manage storage space and maintain data organization.

Instructions

Delete a blob from Blob Storage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
container_nameYesName of the Blob Storage container
blob_nameYesName of the blob to delete

Implementation Reference

  • mcp_server_azure/azure_server.py:206-211 (handler)
    The core handler logic for the 'blob_delete' tool. It retrieves the blob client using the provided container and blob names, deletes the blob, and prepares a success response.
    elif name == "blob_delete":
    blob_client = blob_service_client.get_blob_client(
        container=arguments["container_name"], blob=arguments["blob_name"]
    )
    blob_client.delete_blob()
    response = {"blob_name": arguments["blob_name"], "deleted": True}
  • mcp_server_azure/azure_tools.py:62-79 (schema)
    Defines the Tool object for 'blob_delete' with input schema specifying required container_name and blob_name parameters.
    Tool(
    name="blob_delete",
    description="Delete a blob from Blob Storage",
    inputSchema={
        "type": "object",
        "properties": {
            "container_name": {
                "type": "string",
                "description": "Name of the Blob Storage container",
            },
            "blob_name": {
                "type": "string",
                "description": "Name of the blob to delete",
            },
        },
        "required": ["container_name", "blob_name"],
    },
),
  • mcp_server_azure/azure_server.py:172-176 (registration)
    MCP server registration of tools via @server.list_tools(), which includes 'blob_delete' from get_azure_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

Tool Definition Quality

C2.9/5.0
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 'Delete' implies a destructive mutation, it doesn't specify whether the deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting other blobs). For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

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, direct sentence with zero waste—it states the action and resource without fluff. It's appropriately sized for a simple tool and front-loaded with the core purpose, making it easy for an agent 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?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover critical aspects like return values (e.g., success/failure indicators), error conditions, or behavioral nuances (e.g., idempotency). For a mutation tool with no structured safety hints, more context is needed to ensure reliable use.

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 both parameters (container_name, blob_name) clearly documented in the schema. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. This meets the baseline score of 3 when the schema does 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 clearly states the action ('Delete') and resource ('a blob from Blob Storage'), making the purpose immediately understandable. It distinguishes from siblings like blob_container_delete (which deletes containers) and blob_read/list/upload (which perform different operations). However, it doesn't specify whether this deletes a single blob or has broader scope, 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the blob to exist), exclusions (e.g., not for containers), or sibling tools like blob_container_delete for container deletion. Without such context, an agent might misuse it or overlook better options.

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