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
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Delete an ADLS2 filesystem from Azure Data Lake Storage Gen2 by providing the filesystem name. Ideal for cleaning up unused storage.
Delete an ADLS2 filesystem
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description merely states deletion without disclosing consequences, failure conditions, or permissions needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely short and direct, but front-loads the core action. Small sacrifice in completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Leaves out return behavior and edge cases; minimal info for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
0% schema description coverage; description adds no meaning beyond parameter name and type.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 (ADLS2 filesystem), distinguishing it from sibling tools like delete_directory.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use or prerequisites (e.g., filesystem must be empty). Agent has no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/erikhoward/adls-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server