Skip to main content
Glama
Sign In
ADLS2 MCP Server

ADLS2 MCP Server

by erikhoward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_directory

Remove a directory from an Azure Data Lake Storage Gen2 filesystem by specifying the filesystem name and directory path.

Instructions

Delete a directory from the specified 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": {
      "filesystem": "<filesystem>",
      "path": "<path>"
    },
    "name": "delete_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesystemYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.6/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 for behavioral disclosure. It only states 'delete' without mentioning potential side effects (e.g., recursive deletion, permissions required, error conditions).

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 very concise (one sentence) but this comes at the cost of necessary detail. It is front-loaded but insufficient for safe use.

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 (delete), the description is incomplete. It lacks output spec, parameter details, and any behavioral notes beyond the basic action.

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

Parameters2/5

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

With 0% schema description coverage, the description should define parameter meanings explicitly. It only hints at 'path' being a directory path and 'filesystem' being the target, but no format or constraints are provided.

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 identifies the action (delete) and resource (directory) with a specific filesystem context. It distinguishes from sibling tools like 'delete_filesystem' and 'create_directory'.

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 on when to use this tool versus alternatives, nor any prerequisites or conditions (e.g., whether the directory must be empty). The agent lacks context to decide safely.

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

Deploy Server

Other Tools