ADLS2 MCP Server

delete_filesystem

Delete an ADLS2 filesystem from Azure Data Lake Storage Gen2 by providing the filesystem name. Ideal for cleaning up unused storage.

Instructions

Delete an ADLS2 filesystem

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "delete_filesystem"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jun 4, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description must bear the full burden of behavioral disclosure. The description only indicates deletion, but fails to mention irreversible data loss, required permissions, handling of non-existent filesystems, or any side effects. This is a critical gap for a destructive operation.

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

Conciseness3/5

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

The description is extremely concise (5 words), but conciseness should not come at the cost of essential information. It is front-loaded but fails to provide value beyond the tool's name, thus not fully earning its place.

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 simplicity (single parameter, no output schema), the description should at least note operation irreversibility, success/error behavior, or prerequisites like filesystem existence. It omits all such context, making it incomplete for safe invocation.

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

Parameters1/5

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

The input schema has 0% description coverage, and the tool description adds no meaning to the single 'name' parameter. It does not specify expected format (e.g., full path vs. short name) or constraints, leaving the parameter completely underspecified.

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

Purpose5/5

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

The description clearly states 'Delete an ADLS2 filesystem', specifying a concrete verb (Delete) and resource (ADLS2 filesystem). This distinguishes it from sibling tools like delete_directory or create_filesystem, as it targets filesystems specifically.

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 (e.g., delete_directory for subdirectories, or other deletion methods). There are no prerequisites, context hints, or when-not-to-use instructions, leaving the agent to guess appropriate conditions.

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

Deploy Server