Skip to main content
Glama
JustTryAI

Databricks MCP Server

start_cluster

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

Instructions

Start a terminated Databricks cluster with parameter: cluster_id (required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • MCP tool handler for 'start_cluster'. Registers the tool using @self.tool decorator and implements the execution logic by calling the underlying clusters.start_cluster API and formatting the response as MCP TextContent.
    @self.tool(
        name="start_cluster",
        description="Start a terminated Databricks cluster with parameter: cluster_id (required)",
    )
    async def start_cluster(params: Dict[str, Any]) -> List[TextContent]:
        logger.info(f"Starting cluster with params: {params}")
        try:
            result = await clusters.start_cluster(params.get("cluster_id"))
            return [{"text": json.dumps(result)}]
        except Exception as e:
            logger.error(f"Error starting cluster: {str(e)}")
            return [{"text": json.dumps({"error": str(e)})}]
  • Core implementation of cluster starting logic. Makes a POST request to the Databricks Clusters API endpoint /api/2.0/clusters/start with the cluster_id.
    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})
  • Registration of the 'start_cluster' tool in the DatabricksMCPServer using the FastMCP @tool decorator, specifying name and description.
    @self.tool(
        name="start_cluster",
        description="Start a terminated Databricks cluster with parameter: cluster_id (required)",
    )
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 is to start a cluster, implying a mutation operation, but fails to disclose critical traits such as permissions required, whether it's idempotent, potential side effects (e.g., costs, time to start), or response format. This leaves significant gaps for a tool that performs a state change.

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, straightforward sentence that efficiently conveys the core action and required parameter without unnecessary words. It's appropriately sized for the tool's complexity, though it could be more front-loaded with key details like behavioral traits.

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 tool's complexity (a mutation operation to start a cluster), lack of annotations, no output schema, and low schema description coverage, the description is incomplete. It omits essential context such as behavioral implications, error conditions, or how to verify success, making it inadequate for safe and effective use by an AI agent.

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 schema description coverage is 0%, and the description only mentions 'cluster_id (required)' without explaining what this parameter represents (e.g., a specific cluster identifier), its format, or how to obtain it. Given the low coverage and the presence of a nested object 'params' in the schema, the description adds minimal value beyond stating the parameter name, failing to compensate for the schema's lack of detail.

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 resource ('a terminated Databricks cluster'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'create_cluster' (which creates new clusters) or 'terminate_cluster' (which stops clusters), missing explicit sibling distinction that would warrant a 5.

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 minimal guidance by mentioning the required parameter 'cluster_id' but offers no explicit context on when to use this tool versus alternatives like 'create_cluster' for new clusters or 'get_cluster' for checking status. There's no mention of prerequisites (e.g., cluster must be terminated) or exclusions, 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/JustTryAI/databricks-mcp-server'

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