Skip to main content
Glama
srthkdev

DBeaver MCP Server

by srthkdev

execute_query

Execute read-only SQL queries on DBeaver database connections to retrieve data from 200+ database types without additional configuration.

Instructions

Execute a SQL query on a specific DBeaver connection (read-only queries)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesThe ID or name of the DBeaver connection to use
maxRowsNoMaximum number of rows to return (default: 1000)
queryYesThe SQL query to execute (SELECT statements only)

Implementation Reference

  • Tool definition and input schema for 'execute_query', specifying required connectionId and query parameters with optional maxRows.
    {
      name: 'execute_query',
      description: 'Execute a SQL query on a specific DBeaver connection (read-only queries)',
      inputSchema: {
        type: 'object',
        properties: {
          connectionId: {
            type: 'string',
            description: 'The ID or name of the DBeaver connection to use',
          },
          query: {
            type: 'string',
            description: 'The SQL query to execute (SELECT statements only)',
          },
          maxRows: {
            type: 'number',
            description: 'Maximum number of rows to return (default: 1000)',
            default: 1000
          }
        },
        required: ['connectionId', 'query'],
      },
    },
  • src/index.ts:487-492 (registration)
    Registration and dispatching logic in the CallToolRequest handler that routes 'execute_query' calls to the handleExecuteQuery method.
    case 'execute_query':
      return await this.handleExecuteQuery(args as { 
        connectionId: string; 
        query: string; 
        maxRows?: number 
      });
  • Primary handler for execute_query: sanitizes inputs, validates query, ensures connection exists, optionally adds LIMIT, executes query via DBeaverClient, and formats response.
    private async handleExecuteQuery(args: { 
      connectionId: string; 
      query: string; 
      maxRows?: number 
    }) {
      const connectionId = sanitizeConnectionId(args.connectionId);
      const query = args.query.trim();
      const maxRows = args.maxRows || 1000;
      
      // Validate query
      const validationError = validateQuery(query);
      if (validationError) {
        throw new McpError(ErrorCode.InvalidParams, validationError);
      }
      
      const connection = await this.configParser.getConnection(connectionId);
      if (!connection) {
        throw new McpError(ErrorCode.InvalidParams, `Connection not found: ${connectionId}`);
      }
      
      // Add LIMIT clause if not present and it's a SELECT query
      let finalQuery = query;
      if (query.toLowerCase().trimStart().startsWith('select') && 
          !query.toLowerCase().includes('limit')) {
        finalQuery = `${query} LIMIT ${maxRows}`;
      }
      
      const result = await this.dbeaverClient.executeQuery(connection, finalQuery);
      
      const response = {
        query: finalQuery,
        connection: connection.name,
        executionTime: result.executionTime,
        rowCount: result.rowCount,
        columns: result.columns,
        rows: result.rows,
        truncated: result.rows.length >= maxRows
      };
      
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(response, null, 2),
        }],
      };
    }
  • Supporting method executeQuery in DBeaverClient that handles actual query execution using native tools based on database driver (SQLite/PostgreSQL), called by the main handler.
    async executeQuery(connection: DBeaverConnection, query: string): Promise<QueryResult> {
      const startTime = Date.now();
      
      try {
        // Use native database tools instead of DBeaver command line
        const result = await this.executeWithNativeTool(connection, query);
        result.executionTime = Date.now() - startTime;
        return result;
      } catch (error) {
        throw new Error(`Query execution failed: ${error}`);
      }
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the read-only constraint and connection-specific execution, but doesn't mention authentication needs, rate limits, error handling, or what happens with large result sets beyond the maxRows parameter. It provides basic behavioral context but lacks depth for a mutation-like operation.

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 front-loads the core purpose and key constraint. Every word earns its place with zero waste, making it easy for an agent to parse quickly.

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?

For a query execution tool with no annotations and no output schema, the description provides basic purpose and constraints but lacks information about return format, error cases, or execution limits beyond maxRows. Given the complexity of database operations and absence of structured safety hints, more context would be beneficial.

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%, so the schema already documents all parameters thoroughly. The description adds marginal value by reinforcing the 'SELECT statements only' constraint for the query parameter, but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Execute a SQL query'), the target resource ('on a specific DBeaver connection'), and distinguishes it from siblings by specifying 'read-only queries' (vs. write operations like create_table or drop_table). It provides verb+resource+scope differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('read-only queries'), which implicitly distinguishes it from write operations like alter_table or drop_table. However, it doesn't explicitly name alternatives or state when-not-to-use scenarios beyond the read-only constraint.

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