Skip to main content
Glama
samhavens

Databricks MCP Server

by samhavens

list_files

Browse and view files and directories in Databricks DBFS to manage data storage and access within the Databricks environment.

Instructions

List files and directories in DBFS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbfs_pathNo/

Implementation Reference

  • The MCP tool handler for 'list_files', registered via @mcp.tool() decorator. Calls the underlying dbfs.list_files helper and returns JSON response.
    @mcp.tool()
    async def list_files(dbfs_path: str = "/") -> str:
        """List files and directories in DBFS"""
        logger.info(f"Listing files in: {dbfs_path}")
        try:
            result = await dbfs.list_files(dbfs_path)
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error listing files: {str(e)}")
            return json.dumps({"error": str(e)})
  • Supporting helper function in the DBFS API module that performs the actual Databricks API call to list files in DBFS.
    async def list_files(dbfs_path: str) -> Dict[str, Any]:
        """
        List files and directories in a DBFS path.
        
        Args:
            dbfs_path: The path to list
            
        Returns:
            Response containing the directory listing
            
        Raises:
            DatabricksAPIError: If the API request fails
        """
        logger.info(f"Listing files in DBFS path: {dbfs_path}")
        return make_api_request("GET", "/api/2.0/dbfs/list", params={"path": dbfs_path})
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 of behavioral disclosure. While 'List' implies a read-only operation, the description doesn't specify whether this requires authentication, what format the results are returned in, whether there's pagination, rate limits, or any other behavioral characteristics. It's minimally adequate but lacks important operational details.

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

Conciseness5/5

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

The description is extremely concise - a single sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple listing operation and front-loads the essential information.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what the tool returns, how to interpret results, or provide any context about the DBFS environment. While the tool appears simple, the description leaves too many operational questions unanswered.

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?

The description provides no information about the single parameter 'dbfs_path'. With 0% schema description coverage and no parameter information in the description, the agent has no semantic understanding of what this parameter does or how to use it effectively. The description doesn't compensate for the schema's lack of documentation.

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 ('List') and the resource ('files and directories in DBFS'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from 'list_volume_files' which appears to be a sibling tool for listing files in a different location (volume vs DBFS).

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of when to choose 'list_files' over 'list_volume_files' or other listing tools like 'list_clusters', 'list_jobs', etc. No prerequisites, exclusions, or context for usage is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samhavens/databricks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server