Skip to main content
Glama
srthkdev

DBeaver MCP Server

by srthkdev

list_connections

Retrieve all configured DBeaver database connections to access and query multiple database types through existing setups.

Instructions

List all available DBeaver database connections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeDetailsNoInclude detailed connection information

Implementation Reference

  • The primary handler function that executes the list_connections tool. It parses all DBeaver connections using configParser and returns either full details or a simplified list based on the includeDetails parameter.
    private async handleListConnections(args: { includeDetails?: boolean }) {
      const connections = await this.configParser.parseConnections();
      
      if (args.includeDetails) {
        return {
          content: [{
            type: 'text' as const,
            text: JSON.stringify(connections, null, 2),
          }],
        };
      }
      
      const simplified = connections.map(conn => ({
        id: conn.id,
        name: conn.name,
        driver: conn.driver,
        host: conn.host,
        database: conn.database,
        folder: conn.folder
      }));
      
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(simplified, null, 2),
        }],
      };
    }
  • The input schema definition for the list_connections tool, specifying an optional boolean parameter includeDetails.
    inputSchema: {
      type: 'object',
      properties: {
        includeDetails: {
          type: 'boolean',
          description: 'Include detailed connection information',
          default: false
        }
      }
    },
  • src/index.ts:193-205 (registration)
    The tool registration in the ListToolsRequestSchema response, defining name, description, and input schema for list_connections.
    {
      name: 'list_connections',
      description: 'List all available DBeaver database connections',
      inputSchema: {
        type: 'object',
        properties: {
          includeDetails: {
            type: 'boolean',
            description: 'Include detailed connection information',
            default: false
          }
        }
      },
  • src/index.ts:481-482 (registration)
    The dispatch case in the CallToolRequestSchema handler that routes list_connections calls to the handleListConnections method.
    case 'list_connections':
      return await this.handleListConnections(args as { includeDetails?: boolean });
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List all available' implies a read-only operation, it doesn't specify whether this requires authentication, what format the output takes (e.g., list of names vs. full objects), or if there are any rate limits or performance considerations. For a tool with zero annotation coverage, this leaves significant gaps.

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 with zero wasted words. It's appropriately sized for a simple listing tool and front-loaded with the essential information.

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 low complexity (single optional parameter, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks behavioral details (like output format or authentication needs) and usage guidance relative to siblings. For a simple read operation, this is adequate but with clear gaps.

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?

Schema description coverage is 100%, with the single parameter 'includeDetails' clearly documented in the schema. The description doesn't add any parameter information beyond what the schema provides, which is acceptable given the high schema coverage. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 ('all available DBeaver database connections'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_connection_info' or 'test_connection' that also deal with connections, missing an opportunity for sibling differentiation.

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. With sibling tools like 'get_connection_info' (which might retrieve details for a specific connection) and 'test_connection' (which might verify connectivity), there's no indication of when 'list_connections' is appropriate versus these other tools.

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/srthkdev/omnisql-mcp'

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