Skip to main content
Glama

list_databricks_tools

Discover available Databricks MCP tools after authentication to access and interact with Databricks-hosted applications through Claude.

Instructions

List all available tools on the remote Databricks MCP server. Must authenticate first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function implementing the list_databricks_tools tool. It lists all discovered remote tools with their names, descriptions, and input parameters if available. Requires prior authentication.
    @mcp.tool()
    def list_databricks_tools() -> str:
        """
        List all available tools on the remote Databricks MCP server.
        Must authenticate first.
        """
        if not state.authenticated or not state.proxy:
            return "Not authenticated. Call 'authenticate' first."
        
        if not state.proxy.tools:
            return "No tools available."
        
        lines = [f"Available tools ({len(state.proxy.tools)}):\n"]
        for tool in state.proxy.tools:
            lines.append(f"**{tool.name}**")
            lines.append(f"  {tool.description}")
            if tool.input_schema.get("properties"):
                lines.append(f"  Parameters: {list(tool.input_schema['properties'].keys())}")
            lines.append("")
        
        return "\n".join(lines)
  • The authenticate tool handler which initializes the proxy, connects, and calls discover_tools to populate the list of remote tools used by list_databricks_tools.
    @mcp.tool()
    def authenticate() -> str:
        """
        Authenticate with Databricks using OAuth U2M flow.
        Opens a browser for authorization.
        Uses DATABRICKS_HOST and DATABRICKS_APP_URL from app.yaml or environment.
        """
        try:
            host = state.host or os.environ.get("DATABRICKS_HOST")
            app_url = state.app_url or os.environ.get("DATABRICKS_APP_URL")
            scopes = state.scopes or os.environ.get("DATABRICKS_SCOPES", DEFAULT_SCOPES)
            
            if not host:
                return "Error: DATABRICKS_HOST not configured. Set it in app.yaml or environment."
            if not app_url:
                return "Error: DATABRICKS_APP_URL not configured. Set it in app.yaml or environment."
            
            print(f"Starting OAuth flow for {host}...", file=sys.stderr)
            access_token = start_oauth_flow(host, scopes)
            
            state.proxy = DatabricksMCPProxy(host, app_url, access_token)
            state.proxy.connect()
            state.proxy.discover_tools()
            state.authenticated = True
            
            tool_names = [t.name for t in state.proxy.tools]
            return f"Authenticated successfully!\n\nAvailable tools ({len(tool_names)}):\n" + "\n".join(f"  - {name}" for name in tool_names)
        
        except Exception as e:
            state.authenticated = False
            return f"Authentication failed: {e}"
  • The @mcp.tool() decorator registers the list_databricks_tools function with the FastMCP server instance.
    @mcp.tool()
    def list_databricks_tools() -> str:
        """
        List all available tools on the remote Databricks MCP server.
        Must authenticate first.
        """
        if not state.authenticated or not state.proxy:
            return "Not authenticated. Call 'authenticate' first."
        
        if not state.proxy.tools:
            return "No tools available."
        
        lines = [f"Available tools ({len(state.proxy.tools)}):\n"]
        for tool in state.proxy.tools:
            lines.append(f"**{tool.name}**")
            lines.append(f"  {tool.description}")
            if tool.input_schema.get("properties"):
                lines.append(f"  Parameters: {list(tool.input_schema['properties'].keys())}")
            lines.append("")
        
        return "\n".join(lines)
Behavior3/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 mentions the authentication requirement, which is a key behavioral trait, but lacks details on rate limits, error handling, or what 'list all' entails (e.g., pagination, format). The description doesn't contradict annotations, but it's minimal beyond the auth note.

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 two sentences, front-loaded with the core purpose and followed by a critical prerequisite. Every word earns its place, with no redundancy or fluff. It's efficiently structured for quick comprehension by an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is reasonably complete. It covers the purpose and a key prerequisite. The output schema likely handles return values, so the description doesn't need to explain them. However, it could benefit from more behavioral context, such as response format hints.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is given since the schema fully covers the lack of parameters, and the description doesn't need to compensate.

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 all available tools') and resource ('on the remote Databricks MCP server'), making the purpose immediately understandable. It distinguishes from sibling tools like 'authenticate' and 'call_databricks_tool' by focusing on listing rather than authentication or execution. However, it doesn't specify the exact scope or format of what 'tools' means, keeping it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Must authenticate first,' providing clear prerequisite guidance for when to use this tool. This directly addresses the relationship with the sibling 'authenticate' tool, indicating that authentication is required before invocation. No alternatives are mentioned, but the guidance is specific and actionable.

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/smaheshwari-ux/databricks-mcp-proxy'

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