Skip to main content
Glama
Sign In
dbeaver-mcp

dbeaver-mcp

by bnuprst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List schemas

list_schemas
Read-only

Discover available schemas in a DBeaver connection and see table/view counts for each, optionally including system schemas.

Instructions

Lists schemas in the connection's database with how many tables/views each has.

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

Input Schema

NameRequiredDescriptionDefault
connectionYesDBeaver connection name (as shown in DBeaver), its id, or project/name. See list_connections.
include_systemNoAlso show system schemas (pg_catalog, information_schema...). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/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 the safety profile is covered. The description adds the useful return-content detail that each schema comes with table/view counts, which matters because there is no output schema. It does not mention ordering, pagination, or what happens for an invalid connection name.

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?

One sentence, no filler, and the key differentiator (table/view counts) is packed into the same clause rather than buried. Nothing to cut.

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 two-parameter read-only listing tool with full schema coverage and clear annotations, the description is essentially sufficient, and it usefully signals the return shape via 'how many tables/views each has'. Minor gaps only: no mention of result ordering or behavior on an unknown connection.

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% — both `connection` (name/id/project-name, with a pointer to list_connections) and `include_system` (default false, examples given) are fully documented in the schema. The description adds no parameter meaning beyond that, 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 sentence names a specific verb (Lists) and resource (schemas in the connection's database) and adds the distinctive payload detail — table/view counts per schema. That separates it cleanly from list_connections and list_tables. It stops short of explicitly contrasting with those siblings, so it's clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the discovery step before list_tables or describe_table, but the description never says so, never names an alternative, and gives no exclusions or prerequisites. The 'See list_connections' hint lives in the schema, not the description.

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