Skip to main content
Glama
Sign In
ADLS2 MCP Server

ADLS2 MCP Server

by erikhoward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_file

Download a file from Azure Data Lake Storage Gen2. Provide the filesystem, source file path, and local download path.

Instructions

Download a file from ADLS2

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>",
      "source": "<source>",
      "download_path": "<download_path>"
    },
    "name": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesystemYes
sourceYes
download_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states a basic action without mentioning side effects, permissions, overwrite behavior, or network implications. This is insufficient for safe usage.

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 a single concise sentence, which is appropriately short. However, it lacks important details that could be added without breaking conciseness, such as parameter clarification.

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 three required parameters and no annotations or output schema, the description should provide more context about parameter values, return type, and error conditions. It is incomplete for agentic use.

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 for all three parameters (source, filesystem, download_path). The description does not explain the format, constraints, or meaning of these parameters, leaving the agent to guess.

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 'Download' and the resource 'file from ADLS2', which is specific and distinct from sibling tools like upload_file. However, it could be more precise by indicating the direction (from cloud to local).

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, prerequisites (e.g., file existence), or when not to use it (e.g., large files). The sibling list includes many file operations, but the description offers no differentiation or context.

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