Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by apsolut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

write_query

Execute INSERT, UPDATE, DELETE, and DDL statements on a specified database connection, with multi-statement transactions and confirmation required for destructive operations.

Instructions

Run INSERT/UPDATE/DELETE/DDL. Requires an exact connection name or id. Several statements in one string run on one connection; more than one write is wrapped in a transaction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "query": "<query>"
    },
    "name": "write_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact connection name or id (no partial matching for writes)
queryYesMutating SQL (one or more statements)
confirmNoRequired (true) for destructive statements: DROP, TRUNCATE, ALTER SYSTEM, or DELETE/UPDATE without WHERE
timeoutMsNoStatement timeout in ms (default 30000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses transaction wrapping and the exact-connection requirement, which are useful behavioral traits. However, it doesn't mention the confirm parameter's role in destructive statements (though schema covers it) or any side effects/permissions. The transaction info adds value beyond schema, but more could be said about error handling 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?

Two sentences, front-loaded with the core purpose. Every clause adds value—purpose, connection requirement, and transaction behavior. No fluff or redundancy.

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

Completeness4/5

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

For a 4-parameter tool with no output schema and no annotations, the description covers the essential behavioral context: what it executes, connection requirements, and transaction semantics. It doesn't explain the confirm parameter's necessity for destructive statements (but schema does) and omits return-value details (no output schema). Overall, it's complete enough for an agent to call it correctly.

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%, so the baseline is 3. The description adds meaning by clarifying that 'name' must be an exact match (no partial matching) and that multiple statements in 'query' run on one connection and are wrapped in a transaction. This goes beyond the schema's parameter descriptions, earning a 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 opens with 'Run INSERT/UPDATE/DELETE/DDL', which clearly states the verb and resource. It distinguishes itself from siblings like execute_query (likely read-only) by explicitly targeting mutating SQL, so an agent can immediately tell what it does.

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 on when to use it: it requires an exact connection name or id and explains transaction behavior for multiple statements. It doesn't explicitly contrast with execute_query, but the mutating-SQL focus and sibling names imply the division of labor. Lacks an explicit 'use this for writes, execute_query for reads' statement, so not a 5.

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