Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

search_tables

Find Databricks tables by name using information_schema queries to locate specific data assets across catalogs.

Instructions

Search tables by name (using information_schema)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes
catalogNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the search_tables tool, which queries the information_schema to find tables matching a keyword.
    def search_tables(ctx: Context, keyword: str, catalog: str = None) -> List[Dict[str, Any]]:
        """Search tables by name (using information_schema)"""
        if not catalog:
            raise ToolError("Must specify catalog parameter")
    
        cat = safe_identifier(catalog, "catalog")
        safe_identifier(keyword, "keyword")  # validate only, no quote needed for LIKE
    
        sql = f"""
        SELECT table_catalog, table_schema, table_name, table_type, comment
        FROM {cat}.information_schema.tables
        WHERE table_name LIKE '%{keyword}%'
        LIMIT 50
        """
        return execute_sql(ctx, sql)
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 the tool searches tables by name using information_schema, which implies a read-only operation, but doesn't clarify aspects like permissions required, rate limits, pagination, or what the search returns (e.g., partial matches, case sensitivity). This leaves significant gaps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes a useful technical detail ('using information_schema'). Every word earns its place, making it highly concise and well-structured.

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 tool has an output schema (which should document return values), the description doesn't need to explain outputs. However, with 2 parameters, 0% schema coverage, and no annotations, the description is incomplete—it lacks details on parameter usage, behavioral traits, and differentiation from siblings. It's minimally adequate but has clear gaps for a search tool.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions searching 'by name', which relates to the 'keyword' parameter, but doesn't explain what 'keyword' entails (e.g., substring matching) or the purpose of the 'catalog' parameter. The description adds minimal value beyond the schema, failing to fully address the coverage gap.

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 tool's purpose: 'Search tables by name (using information_schema)'. It specifies the verb ('Search'), resource ('tables'), and scope ('by name'), though it doesn't explicitly differentiate from siblings like 'list_tables' or 'get_table_detail'. The mention of 'information_schema' adds technical context.

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 siblings like 'list_tables' (which might list all tables) or 'get_table_detail' (which might retrieve specific table metadata), nor does it specify prerequisites or exclusions. Usage is implied but not articulated.

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/ChrisChoTW/databricks-mcp'

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