Skip to main content
Glama
JustTryAI

Databricks MCP Server

get_cluster

Retrieve detailed information about a specific Databricks cluster by providing its cluster ID to access configuration, status, and resource details.

Instructions

Get information about a specific Databricks cluster with parameter: cluster_id (required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • Registration of the 'get_cluster' MCP tool with description specifying the required cluster_id parameter.
    @self.tool(
        name="get_cluster",
        description="Get information about a specific Databricks cluster with parameter: cluster_id (required)",
    )
  • Handler function for the 'get_cluster' tool that extracts cluster_id from params, calls the clusters.get_cluster API, and returns JSON response or error.
    async def get_cluster(params: Dict[str, Any]) -> List[TextContent]:
        logger.info(f"Getting cluster info with params: {params}")
        try:
            result = await clusters.get_cluster(params.get("cluster_id"))
            return [{"text": json.dumps(result)}]
        except Exception as e:
            logger.error(f"Error getting cluster info: {str(e)}")
            return [{"text": json.dumps({"error": str(e)})}]
  • Core API helper function that makes the Databricks GET request to /api/2.0/clusters/get with cluster_id.
    async def get_cluster(cluster_id: str) -> Dict[str, Any]:
        """
        Get information about a specific cluster.
        
        Args:
            cluster_id: ID of the cluster
            
        Returns:
            Response containing cluster information
            
        Raises:
            DatabricksAPIError: If the API request fails
        """
        logger.info(f"Getting information for cluster: {cluster_id}")
        return make_api_request("GET", "/api/2.0/clusters/get", params={"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 this is a 'Get information' operation which implies read-only behavior, but doesn't disclose any behavioral traits like whether it requires specific permissions, what happens if the cluster doesn't exist, rate limits, or what format the information is returned in. The description is minimal and leaves critical behavioral aspects unspecified.

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 appropriately concise with just one sentence that states the purpose and mentions the required parameter. It's front-loaded with the core functionality. While it could be more informative, every word serves a purpose and there's no wasted text.

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 cluster operations, no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't explain what information is returned, how to interpret results, error conditions, or how this differs from other cluster tools. For a tool that presumably returns detailed cluster configuration and status information, this description leaves too much unspecified.

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% with 1 parameter, and the description mentions 'cluster_id (required)' which adds some semantic meaning beyond the schema. However, it doesn't explain what format the cluster_id should be in, where to find it, or provide any examples. For a single parameter tool with zero schema coverage, this minimal information is insufficient to compensate adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get information about a specific Databricks cluster' which provides a clear verb ('Get information') and resource ('Databricks cluster'), but it doesn't distinguish this from sibling tools like 'list_clusters' or 'start_cluster'. It's vague about what specific information is retrieved compared to alternatives.

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 like 'list_clusters' or 'start_cluster'. It mentions the required parameter 'cluster_id' but doesn't explain when this tool is appropriate versus other cluster-related operations available in the sibling tool list.

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