Skip to main content
Glama
samhavens

Databricks MCP Server

by samhavens

start_cluster

Start a terminated Databricks cluster by providing its cluster ID to resume data processing and analytics workflows.

Instructions

Start a terminated Databricks cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cluster_idYes

Implementation Reference

  • MCP tool handler for start_cluster that wraps the core API call, handles errors, and returns JSON response.
    @mcp.tool()
    async def start_cluster(cluster_id: str) -> str:
        """Start a terminated Databricks cluster"""
        logger.info(f"Starting cluster: {cluster_id}")
        try:
            result = await clusters.start_cluster(cluster_id)
            return json.dumps(result)
        except Exception as e:
            logger.error(f"Error starting cluster: {str(e)}")
            return json.dumps({"error": str(e)})
  • Core implementation that performs the actual Databricks API request to start the cluster.
    async def start_cluster(cluster_id: str) -> Dict[str, Any]:
        """
        Start a terminated Databricks cluster.
        
        Args:
            cluster_id: ID of the cluster to start
            
        Returns:
            Empty response on success
            
        Raises:
            DatabricksAPIError: If the API request fails
        """
        logger.info(f"Starting cluster: {cluster_id}")
        return make_api_request("POST", "/api/2.0/clusters/start", data={"cluster_id": cluster_id})
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Start') but doesn't mention permissions required, whether it's idempotent, rate limits, or what happens if the cluster isn't terminated. This leaves significant gaps for a mutation tool.

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 that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy to understand 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 complexity of starting a cluster (a mutation operation), no annotations, no output schema, and minimal parameter coverage, the description is inadequate. It should explain more about behavior, outcomes, or error conditions to be complete.

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 description doesn't add any parameter details beyond the schema, but with only 1 parameter and 0% schema description coverage, the baseline is high. The tool name and description imply 'cluster_id' refers to a terminated cluster, which adds minimal context, keeping it near the baseline.

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 ('Start') and the resource ('a terminated Databricks cluster'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from siblings like 'create_cluster' or 'run_job', which might involve cluster operations, so it misses full 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 such as 'create_cluster' for new clusters or 'run_job' for job execution. It lacks any context about prerequisites, exclusions, or typical scenarios, leaving usage 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