Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by apsolut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_tables

Retrieve all table names in a specified schema of a DBeaver connection to map your database structure.

Instructions

List tables in a schema for a DBeaver connection.

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

Input Schema

NameRequiredDescriptionDefault
nameYesConnection name or id
schemaNoSchema name (default: connection schema or public)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A3.7/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 states a read-only action ('list') which implies non-destructive behavior, but does not disclose return format, whether it includes views or system tables, or any connection prerequisites. The description is not misleading but is sparse on behavioral detail.

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 that immediately states the purpose. No wasted words and no redundancy with the schema. It is optimally front-loaded.

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?

Given no output schema and no annotations, the description should clarify what the tool returns (e.g., a list of table names) and any prerequisites (e.g., an active connection). It only says 'list tables,' which is a minimal definition but leaves some ambiguity about the exact output structure. For a simple list operation, this is adequate but not fully complete.

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 both parameters are already described in the input schema. The description does not add any additional meaning to the parameters beyond what the schema provides, matching the baseline for high coverage.

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 clearly states the action ('List tables') and the resource ('in a schema for a DBeaver connection'), which is specific and distinguishes it from sibling tools like list_schemas and describe_table. It fully conveys what the tool does.

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

Usage Guidelines3/5

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

The description implies usage (when you need to list tables) but does not explicitly mention when not to use it or alternatives like list_schemas or describe_table. No exclusions or alternative routing is provided, so it relies on inference.

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