Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by bnuprst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find columns by name

find_columns
Read-only

Search column names and comments across all tables and views to locate every table containing a specific column, such as policy_id, using a connection and pattern.

Instructions

Searches column names (and column comments) across all tables and views, e.g. to find every table that has a 'policy_id' column.

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": {
      "connection": "<connection>",
      "pattern": "<pattern>"
    },
    "name": "find_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 200.
schemaNoOnly this schema.
patternYes'policy_id' = contains, 'policy*' = starts with, or a LIKE pattern with % (case-insensitive).
connectionYesDBeaver connection name (as shown in DBeaver), its id, or project/name. See list_connections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful scope details: column comments are searched and the search spans all tables and views. It does not disclose result format, ordering, or large-result behavior beyond the schema's limit parameter.

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 with the core action front-loaded and a practical example attached. There is no redundant or wasted text.

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 simple read-only search tool, the description plus annotations and schema provide enough to call it correctly. It could be slightly more complete by mentioning the limit/default behavior or typical result shape, but no critical information is missing.

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 coverage is 100%, so parameters like pattern, connection, schema, and limit are fully documented in the schema. The description does not add syntax or semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 states a specific verb and resource: it searches column names and comments across all tables and views. The example clarifies the intended outcome, though it does not explicitly contrast with siblings such as describe_table or list_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?

It provides a clear usage example: finding every table with a 'policy_id' column. It does not state when-not to use it or name alternatives, but the context for use is clear.

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