Skip to main content
Glama
Mhdd-24

@mhdd_24/dbeaver-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

db_describe_table

Get column definitions for a table or view, including names and types, with optional schema, database, or profile overrides to target the right database.

Instructions

Describe columns for a table or view. Optional schema, database, and/or profile override.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesTable or view name
schemaNoSchema name (default: public)
profileNoConnection profile: "dev" | "qa" | "default". Uses credentials from mcp.json (DBEAVER_DEV_* / DBEAVER_QA_* or PG_DEV_* / PG_QA_*). Omit to use the sticky session profile from db_set_profile / DBEAVER_PROFILE.
databaseNoOptional database name override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations and no mention of read-only nature, side effects, or error behavior. With no annotations, the description carries full burden but is silent.

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?

Single concise sentence that fronts the purpose before optionality. No fluff.

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

Completeness2/5

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

No output schema or description of returned column details (names, types, etc.). Also lacks guidance on when to prefer this over listing tables or querying.

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 covers all 4 parameters at 100% coverage. Descriptions add some details (e.g., default for schema, profile credential reference), but tool-level description adds little beyond repeating optionality.

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?

Clear verb 'Describe' with specific object (columns) and resource (table/view). Scope is unambiguous.

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?

Implies use for column information, but does not explicitly differentiate from sibling tools like db_list_tables or db_query.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools