Skip to main content
Glama

databricks_get_catalog_info

Retrieve detailed information about a Databricks Unity Catalog including schema structure and metadata for data management and analysis workflows.

Instructions

Get detailed information about a Databricks catalog.

Args: catalog_name: Catalog name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalog_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation in DatabricksTools class that retrieves detailed catalog information using the Databricks SDK.
    async def get_catalog_info(self, catalog_name: str) -> Dict[str, Any]:
        """
        Get detailed information about a catalog.
    
        Args:
            catalog_name: Catalog name
    
        Returns:
            Catalog information
        """
        self._check_client()
    
        try:
            catalog = self.client.catalogs.get(name=catalog_name)
    
            result = {
                "name": catalog.name,
                "comment": catalog.comment,
                "owner": catalog.owner,
                "created_at": catalog.created_at,
                "updated_at": catalog.updated_at,
                "storage_root": catalog.storage_root,
            }
    
            # Add properties if available
            if hasattr(catalog, "properties") and catalog.properties:
                result["properties"] = catalog.properties
    
            return result
    
        except Exception as e:
            logger.error(f"Databricks API error: {e}")
            raise ValueError(f"Failed to get catalog info: {str(e)}")
  • MCP server tool registration and thin wrapper handler delegating to DatabricksTools.get_catalog_info
    @mcp.tool()
    async def databricks_get_catalog_info(catalog_name: str) -> dict:
        """Get detailed information about a Databricks catalog.
    
        Args:
            catalog_name: Catalog name
        """
        return await databricks_tools.get_catalog_info(catalog_name=catalog_name)
  • Input schema definition for the tool used in Anthropic Claude integration.
    {
        "name": "databricks_get_catalog_info",
        "description": "Get detailed information about a Databricks catalog",
        "input_schema": {
            "type": "object",
            "properties": {
                "catalog_name": {
                    "type": "string",
                    "description": "Catalog name",
                }
            },
            "required": ["catalog_name"],
        },
    },
  • Dispatch logic in llm_assistant.py that calls the tool handler during tool execution.
    elif tool_name == "databricks_get_catalog_info":
        result = await databricks_tools.get_catalog_info(
            catalog_name=tool_input["catalog_name"]
        )
  • Dispatch logic in quick_query.py CLI script that calls the tool handler.
    elif tool_name == "databricks_get_catalog_info":
        result = await databricks.get_catalog_info(
            catalog_name=args["catalog_name"]
        )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying it's read-only, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or what 'detailed information' entails. This is a significant gap for a tool with no annotation coverage.

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 brief and front-loaded with the main purpose, followed by parameter documentation. It avoids unnecessary words, but the structure could be slightly improved by integrating the parameter info more seamlessly rather than as a separate 'Args' block.

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 that there's an output schema (which handles return values), no annotations, and low schema coverage, the description is minimally adequate. It covers the basic purpose and parameter, but lacks details on usage context, behavioral traits, and doesn't fully compensate for the missing annotations, making it incomplete for optimal agent understanding.

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 includes an 'Args' section that documents the single parameter 'catalog_name', but the schema description coverage is 0%, so the schema provides no additional details. The description adds basic meaning by specifying the parameter name, but it doesn't explain format constraints (e.g., string patterns) or provide examples, leaving some ambiguity.

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 ('Get') and resource ('detailed information about a Databricks catalog'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling 'databricks_list_catalogs' (which likely lists catalogs rather than providing detailed info about a specific one), so it doesn't reach the highest score.

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. It doesn't mention sibling tools like 'databricks_list_catalogs' (for listing catalogs) or 'databricks_get_schema_info' (for schema details), nor does it specify prerequisites or contexts for usage.

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/bsangars/mcp'

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