Skip to main content
Glama
Sign In
ADLS2 MCP Server

ADLS2 MCP Server

by erikhoward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

file_exists

Check if a file exists in an ADLS Gen2 filesystem by specifying the filesystem name and file path.

Instructions

Check if a file exists in 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>",
      "file_path": "<file_path>"
    },
    "name": "file_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesystemYes
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic action but does not clarify return values (e.g., boolean), error behavior (e.g., what happens if file missing), or access requirements. For a read operation, this is insufficient.

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

Conciseness4/5

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

The description is a single clear sentence, front-loading the purpose. However, it is overly terse, omitting details that could be added without significant bloat, but it is not verbose.

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 lack of output schema, annotations, and parameter documentation, the description is insufficient for an agent to fully understand behavior. It does not state return type, side effects, or edge cases. For a simple existence check, some context is still needed.

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?

With 0% schema description coverage, the description adds no meaning beyond the parameter names in the schema. It does not explain formats, constraints, or relationships for 'file_path' or 'filesystem'. The schema itself provides titles but no descriptions.

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 the tool's function: 'Check if a file exists in the specified filesystem.' The verb 'Check' and resource 'a file exists' are specific, and it distinguishes from sibling tools like directory_exists and file manipulation operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for existence checks but provides no explicit guidance on when to use it versus alternatives like directory_exists or other file operations. No when-not-to-use or alternative tool references are given.

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