Skip to main content
Glama

blob_read

Retrieve content from Azure Blob Storage by specifying container and blob names to access stored data.

Instructions

Read a blob's content from Blob Storage

Input Schema

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

Implementation Reference

  • Executes the blob_read tool by creating a blob client, downloading the blob content, decoding it as UTF-8, and returning it as TextContent.
    elif name == "blob_read":
        blob_client = blob_service_client.get_blob_client(
            container=arguments["container_name"], blob=arguments["blob_name"]
        )
        downloader = blob_client.download_blob()
        content = downloader.readall().decode("utf-8")
        return [TextContent(type="text", text=content)]
  • Defines the schema for the blob_read tool, including input parameters container_name and blob_name as required strings.
    Tool(
        name="blob_read",
        description="Read a blob's content 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 read",
                },
            },
            "required": ["container_name", "blob_name"],
        },
    ),
  • Registers the blob_read tool (among others) by returning the list of Azure tools from get_azure_tools() in the list_tools handler.
    async def list_tools() -> list[Tool]:
        """List available Azure tools"""
        logger.debug("Handling list_tools request")
        return get_azure_tools()  # Use get_azure_tools
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. It states the action ('Read') but doesn't mention whether this is a safe read operation, potential errors (e.g., if the blob doesn't exist), authentication requirements, rate limits, or the format of the returned content. This leaves significant gaps for an agent to understand the tool's behavior.

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 with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy.

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 address what the tool returns (e.g., raw content, metadata), error conditions, or behavioral nuances. For a read operation with no structured output documentation, more context is needed to guide an agent effectively.

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?

The input schema has 100% description coverage, with clear parameter descriptions in the schema itself. The description doesn't add any meaning beyond what the schema provides, such as explaining the relationship between 'container_name' and 'blob_name' or providing examples. This meets the baseline of 3 when schema coverage is high.

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 ('Read') and resource ('blob's content from Blob Storage'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'blob_list' or 'cosmosdb_item_read', which would require more specificity to earn a 5.

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 an existing blob), exclusions, or comparisons to siblings like 'blob_list' for listing blobs or 'cosmosdb_item_read' for reading from a different service.

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