Skip to main content
Glama
hydrolix

mcp-hydrolix

Official

list_databases

Retrieve a list of available Hydrolix databases to enable schema exploration and data querying within LLM-based workflows via the mcp-hydrolix server.

Instructions

List available Hydrolix databases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_databases' tool. It connects to Hydrolix using the request credential, executes 'SHOW DATABASES', parses the result into a list of database names, and returns them as JSON.
    @mcp.tool()
    def list_databases():
        """List available Hydrolix databases"""
        logger.info("Listing all databases")
        client = create_hydrolix_client(get_request_credential())
        result = client.command("SHOW DATABASES")
    
        # Convert newline-separated string to list and trim whitespace
        if isinstance(result, str):
            databases = [db.strip() for db in result.strip().split("\n")]
        else:
            databases = [result]
    
        logger.info(f"Found {len(databases)} databases")
        return json.dumps(databases)
  • The @mcp.tool() decorator registers this function as an MCP tool named 'list_databases' with the FastMCP server instance.
    @mcp.tool()
    def list_databases():
        """List available Hydrolix databases"""
        logger.info("Listing all databases")
        client = create_hydrolix_client(get_request_credential())
        result = client.command("SHOW DATABASES")
    
        # Convert newline-separated string to list and trim whitespace
        if isinstance(result, str):
            databases = [db.strip() for db in result.strip().split("\n")]
        else:
            databases = [result]
    
        logger.info(f"Found {len(databases)} databases")
        return json.dumps(databases)
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. It mentions 'List available Hydrolix databases' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the return format looks like (e.g., list of names vs. detailed objects). This leaves significant gaps for an agent to understand how to use it effectively.

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 that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple listing tool.

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's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks context. It doesn't explain what 'available' means (e.g., accessible vs. all databases), the return format, or how it relates to siblings. For a tool with no structured data to rely on, more completeness would be helpful.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate here, but it could have mentioned if there are implicit filters or options (e.g., by status). Baseline is 4 for zero parameters with high schema coverage.

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 ('List') and resource ('available Hydrolix databases'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_tables' (which lists tables rather than databases), though the distinction is implied through the resource name.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_tables' or 'run_select_query'. The description only states what it does, without context about prerequisites, timing, or comparisons to siblings.

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

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