Skip to main content
Glama
samhavens

Databricks MCP Server

by samhavens

list_clusters

Retrieve a list of all Databricks clusters to monitor resources, manage configurations, and track cluster status.

Instructions

List all Databricks clusters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_clusters': decorated with @mcp.tool(), logs the action, calls clusters.list_clusters() helper, returns JSON result or error.
    @mcp.tool()
    async def list_clusters() -> str:
        """List all Databricks clusters"""
        logger.info("Listing clusters")
        try:
            result = await clusters.list_clusters()
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error listing clusters: {str(e)}")
            return json.dumps({"error": str(e)})
  • Core helper function that performs the Databricks API GET request to /api/2.0/clusters/list to fetch clusters.
    async def list_clusters() -> Dict[str, Any]:
        """
        List all Databricks clusters.
        
        Returns:
            Response containing a list of clusters
            
        Raises:
            DatabricksAPIError: If the API request fails
        """
        logger.info("Listing all clusters")
        return make_api_request("GET", "/api/2.0/clusters/list")
  • The @mcp.tool() decorator registers the list_clusters function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't describe what 'List all' entails—such as pagination behavior, return format, authentication requirements, or rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 annotations and output schema, the description is incomplete. It doesn't explain what the listing returns (e.g., cluster IDs, names, statuses) or behavioral aspects like ordering or limits. For a tool with no structured data to supplement it, the description should provide more context to be fully helpful.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, earning a baseline score of 4 for not introducing confusion or redundancy.

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 verb ('List') and resource ('Databricks clusters') with scope ('all'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_cluster' (which retrieves a specific cluster) or 'list_jobs' (which lists different resources), missing explicit sibling distinction.

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. It doesn't mention when to use 'list_clusters' instead of 'get_cluster' (for specific cluster details) or other list tools like 'list_jobs', nor does it specify prerequisites or exclusions. This leaves usage context unclear.

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