Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by bnuprst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List DBeaver connections

list_connections
Read-only

Lists DBeaver database connections with engine, environment type, host, database, usability, and read-only enforcement, so you can choose a valid connection before exploring or querying data.

Instructions

Lists the database connections configured in DBeaver that this server may use: name, engine and placeholder style, type (dev/test/prod), host, database, whether it can be used, and how read-only is enforced. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only behavior and a closed-world scope. The description adds useful context by enumerating returned fields, including connection type, usability, and read-only enforcement, which helps the agent understand what it will learn before calling other tools.

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 compact and front-loaded: one sentence describes the resource and returned fields, followed by a short imperative. Every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool with no output schema, the description provides enough detail about what will be returned. Annotations cover the safety profile, so no significant gaps remain.

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 zero parameters, so there are no parameter semantics to document. Per the calibration baseline for 0 params, this scores 4.

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 states a specific verb and resource: listing DBeaver database connections configured for this server. It also distinguishes the tool from sibling tools like list_schemas and list_tables by focusing on connections rather than schemas or tables.

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 instruction 'Call this first' gives clear usage guidance for this zero-parameter discovery tool. It does not explicitly name when not to use it or list alternatives, but the sequencing guidance is strong for its role.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools