Skip to main content
Glama
srthkdev

DBeaver MCP Server

by srthkdev

get_connection_info

Retrieve detailed configuration and properties for a specific DBeaver database connection using its unique ID or name.

Instructions

Get detailed information about a specific DBeaver connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesThe ID or name of the DBeaver connection

Implementation Reference

  • The handler function that executes the get_connection_info tool logic. It sanitizes the connection ID, retrieves the connection details using the config parser, and returns the connection information as JSON.
    private async handleGetConnectionInfo(args: { connectionId: string }) {
      const connectionId = sanitizeConnectionId(args.connectionId);
      const connection = await this.configParser.getConnection(connectionId);
      
      if (!connection) {
        throw new McpError(ErrorCode.InvalidParams, `Connection not found: ${connectionId}`);
      }
      
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(connection, null, 2),
        }],
      };
    }
  • src/index.ts:484-485 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches to the specific get_connection_info handler method.
    case 'get_connection_info':
      return await this.handleGetConnectionInfo(args as { connectionId: string });
  • src/index.ts:207-220 (registration)
    The tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and input schema.
    {
      name: 'get_connection_info',
      description: 'Get detailed information about a specific DBeaver connection',
      inputSchema: {
        type: 'object',
        properties: {
          connectionId: {
            type: 'string',
            description: 'The ID or name of the DBeaver connection',
          },
        },
        required: ['connectionId'],
      },
    },
  • The input schema definition for the get_connection_info tool, specifying the required connectionId parameter.
    inputSchema: {
      type: 'object',
      properties: {
        connectionId: {
          type: 'string',
          description: 'The ID or name of the DBeaver connection',
        },
      },
      required: ['connectionId'],
    },
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 retrieves 'detailed information' but does not specify what that includes (e.g., configuration, status, metadata), whether it's a read-only operation, requires authentication, or has rate limits. This leaves significant gaps for a tool that likely interacts with database connections.

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 unnecessary words. It is front-loaded with the core action and resource, 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 lack of annotations and output schema, the description is incomplete. It does not explain what 'detailed information' entails, the format of the response, or potential errors, which is insufficient for a tool that likely returns structured data about database connections.

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 parameter 'connectionId' clearly documented as 'The ID or name of the DBeaver connection'. The description adds no additional meaning beyond this, such as format examples or constraints, but the schema provides adequate baseline 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 ('Get') and resource ('detailed information about a specific DBeaver connection'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'list_connections' (which likely lists all connections) or 'test_connection' (which might test connectivity), missing full sibling distinction.

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 does not mention when to prefer 'get_connection_info' over 'list_connections' for detailed data or 'test_connection' for status checks, nor does it specify prerequisites or exclusions 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/srthkdev/omnisql-mcp'

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