Skip to main content
Glama
Mhdd-24

@mhdd_24/dbeaver-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

db_query

Run SQL queries against a selected database profile, or switch to dev/qa for a single call. Read-only by default; optionally cap rows and override database without asking for credentials.

Instructions

Run SQL against the sticky session profile (or optional profile=dev|qa for one call). Read-only by default. Optional database name and maxRows. Do not ask the user for connection host/password — use profiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlYesSQL statement to execute
maxRowsNoMax rows to return (default from DBEAVER_QUERY_MAX_ROWS / PG_MAX_ROWS)
profileNoConnection profile: "dev" | "qa" | "default". Uses credentials from mcp.json (DBEAVER_DEV_* / DBEAVER_QA_* or PG_DEV_* / PG_QA_*). Omit to use the sticky session profile from db_set_profile / DBEAVER_PROFILE.
databaseNoOptional database name override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Discloses 'read-only by default' and profile-based connection handling, which are important behavioral traits. Since no annotations are provided, the description carries the burden; it covers key behavior but not full error or return behavior.

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 concise and well-structured, covering purpose, behavior, and constraints in a few sentences with no redundant words.

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?

No output schema exists, and the description does not explicitly mention return format or error behavior. For a query tool the result set is implied, but missing explicit output description lowers completeness.

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?

Schema coverage is 100% with descriptions for all parameters. The description adds valuable context about the sticky session profile and instructs not to ask for credentials, enhancing parameter understanding beyond the schema.

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?

States a specific action (Run SQL) against a profile, clearly distinguishing it from sibling metadata/list/set tools. The description makes it obvious this is the querying tool.

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?

Provides clear guidance to use profiles instead of asking for credentials and explains the profile override mechanism. It does not explicitly contrast with sibling metadata tools, but the context implies when arbitrary SQL is needed.

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