Skip to main content
Glama
Sign In
ADLS2 MCP Server

ADLS2 MCP Server

by erikhoward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

upload_file

Upload a local file to an Azure Data Lake Storage Gen2 filesystem at a specified destination path.

Instructions

Upload a file to 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": {
      "upload_file": "<upload_file>",
      "filesystem": "<filesystem>",
      "destination": "<destination>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_fileYes
filesystemYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must carry full burden. Minimal disclosure: no information on side effects, permissions, or 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.

Conciseness2/5

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

Extremely short but under-specified; conciseness is sacrificed for completeness, missing essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 required parameters and no output schema, the description is woefully incomplete, offering only the barest purpose.

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?

Schema coverage is 0%; description provides no details about parameters (filesystem, destination, upload_file), leaving the agent uninformed about their meaning or constraints.

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 'Upload a file to ADLS2' clearly states the action and target system, but does not differentiate among sibling tools like download_file or rename_file, missing specificity for a file upload tool.

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; lacks context about prerequisites, file size limits, or overwrite behavior.

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