Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by bnuprst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Describe a table or view

describe_table
Read-only

Retrieve a table or view's full schema details—columns, keys, indexes, references, size, and view definition—to inspect database structure before writing queries or migrations.

Instructions

Full structure of one table or view: columns (type, nullable, default, comment), primary/unique/foreign keys, tables referencing it, indexes, size, and the view definition.

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>",
      "table": "<table>"
    },
    "name": "describe_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable or view name, optionally schema-qualified: 'policy' or 'core.policy'.
schemaNoSchema, if not given in 'table'.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds the substantive point that this is a deep, multi-aspect introspection returning keys, referential relationships, indexes, size and view SQL. It does not mention potential cost on very large catalogs, permission requirements, or behavior when the table is missing, which keeps it from a 5.

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?

A single dense sentence that front-loads the resource ('Full structure of one table or view') and then lists contents; no filler and nothing that could be cut without losing information.

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?

With no output schema, the description carries the burden of explaining return contents and does so thoroughly for a read-only introspection tool. Missing only edge-case behavior (table not found, connection lookup failure) and guidance relative to find_columns.

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%, and the schema already explains schema-qualification for 'table', the optional 'schema' fallback, and the 'connection' formats pointing to list_connections. The description adds nothing about parameters, so the baseline 3 applies.

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 enumerates precisely what 'full structure' means (columns with type/nullability/default/comment, keys, referencing tables, indexes, size, view definition), so an agent knows exactly what this returns. It does not explicitly contrast with the overlapping sibling find_columns, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of the siblings find_columns or list_tables that overlap with it. The usage is only inferable from the enumeration of returned structure.

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