Skip to main content
Glama

call_databricks_tool

Execute Databricks-hosted tools through the MCP proxy by specifying tool names and arguments for remote operations.

Instructions

Call a tool on the remote Databricks MCP server.

Args:
    tool_name: Name of the tool to call (use list_databricks_tools to see available tools)
    arguments: Arguments to pass to the tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_nameYes
argumentsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool()-decorated handler function that implements the core logic of 'call_databricks_tool' by checking authentication and proxying the tool call to the DatabricksMCPProxy instance.
    @mcp.tool()
    def call_databricks_tool(tool_name: str, arguments: dict = {}) -> str:
        """
        Call a tool on the remote Databricks MCP server.
        
        Args:
            tool_name: Name of the tool to call (use list_databricks_tools to see available tools)
            arguments: Arguments to pass to the tool
        """
        if not state.authenticated or not state.proxy:
            return "Not authenticated. Call 'authenticate' first."
        
        try:
            result = state.proxy.call_tool(tool_name, arguments)
            
            if hasattr(result, 'content') and result.content:
                texts = [c.text for c in result.content if hasattr(c, 'text')]
                if texts:
                    return "\n".join(texts)
            
            return str(result)
        
        except Exception as e:
            return f"Error calling tool '{tool_name}': {e}"
  • Supporting method in DatabricksMCPProxy class that performs the actual remote tool invocation via DatabricksMCPClient.call_tool in a thread pool.
    def call_tool(self, name: str, arguments: dict) -> Any:
        """Call a tool on the remote MCP server."""
        if not self._mcp_client:
            raise RuntimeError("Not connected. Call connect() first.")
        with ThreadPoolExecutor() as executor:
            return executor.submit(self._mcp_client.call_tool, name, arguments or {}).result()
  • The @mcp.tool() decorator registers the 'call_databricks_tool' function with the FastMCP server.
    @mcp.tool()
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 mentions calling a remote tool but fails to disclose critical traits such as authentication requirements, potential side effects (e.g., whether it's read-only or destructive), error handling, or rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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 appropriately sized and front-loaded, with a clear main sentence followed by concise bullet points for args. Every sentence adds value without redundancy, making it efficient and easy to parse.

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

Completeness3/5

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

Given the complexity of calling remote tools, 2 parameters, no annotations, and an output schema present, the description is somewhat complete but has gaps. It covers the basic purpose and usage but lacks details on authentication, error cases, or behavioral traits, which are crucial for such a tool. The output schema helps, but the description could do more to compensate for missing annotations.

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

Parameters3/5

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

The description adds some meaning beyond the input schema by explaining that tool_name should correspond to tools listed by list_databricks_tools and that arguments are passed to the tool. However, with 0% schema description coverage and 2 parameters (one required), it doesn't fully compensate for the lack of schema details, such as the structure or constraints of arguments.

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 'call' and the resource 'tool on the remote Databricks MCP server', making the purpose specific and understandable. It distinguishes from sibling tools by mentioning list_databricks_tools as a prerequisite for discovering available tools, though it doesn't explicitly differentiate from 'authenticate'.

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

Usage Guidelines4/5

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

The description provides clear context for usage by specifying that list_databricks_tools should be used to see available tools, which implicitly guides when to use this tool. However, it lacks explicit guidance on when not to use it or alternatives, such as how it relates to the authenticate sibling tool.

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