Skip to main content
Glama
burakdirin

clickhouse-mcp-server

connect_database

Establish a connection to a specified ClickHouse database for secure interactions and query execution, facilitating data access and management through the MCP server.

Instructions

Connect to a specific ClickHouse database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseYes

Implementation Reference

  • The connect_database tool handler: switches to the specified database by executing a USE query via the QueryExecutor, returns JSON-formatted result or error message.
    @mcp.tool()
    def connect_database(database: str, ctx: Context) -> str:
        """Connect to a specific ClickHouse database"""
        try:
            executor = _get_executor(ctx)
            result = executor.execute_single_query(f"USE {database}")
            return json.dumps(result, indent=2)
        except (ConnectionError, QueryError) as e:
            return str(e)
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 the action ('Connect') but doesn't describe what the connection entails (e.g., authentication requirements, persistence, rate limits, or what happens on success/failure). This leaves significant gaps for a tool that likely involves network operations.

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 is front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 a database connection tool with no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral nuances, leaving the agent with insufficient context for reliable use.

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%, so the description must compensate. It mentions 'a specific ClickHouse database', which implies the 'database' parameter is a database name, but provides no further details (e.g., format, examples, or constraints). This adds minimal value beyond the schema's basic type information.

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 ('Connect to') and resource ('a specific ClickHouse database'), making the purpose unambiguous. However, it doesn't differentiate from the sibling tool 'execute_query', which might also involve database connections but for query execution rather than establishing a connection.

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 'execute_query'. It lacks context about prerequisites (e.g., whether a connection must be established before querying) or exclusions, leaving usage unclear.

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

Related 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/burakdirin/clickhouse-mcp-server'

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