dbx-mcp

Manage Lakehouse Federation connections

manage_uc_connections

Destructive

Manage Unity Catalog Lakehouse Federation connections to external databases like Snowflake and PostgreSQL. Perform create, read, update, and delete operations with secure credential handling.

Instructions

Manage Unity Catalog Lakehouse Federation connections (Snowflake, PostgreSQL, MySQL, SQL Server, Redshift, BigQuery, Oracle, Teradata, Databricks, ...).

create needs name, connection_type and options; spec may add comment, properties, read_only. update needs the full options map (Databricks replaces it) and spec may set owner/new_name. Credentials in options are sent to Databricks but never returned: responses show only non-secret option keys (host, port, ...). All changes are SECURITY_SENSITIVE; delete is also DESTRUCTIVE.

Safety classification: get, list = READ_ONLY; create, update = SECURITY_SENSITIVE+WRITE; delete = DESTRUCTIVE+SECURITY_SENSITIVE.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Connection name (required except for list).
`spec`	No	Request body fields for create/update, using the Databricks REST API field names (snake_case). Unknown fields are rejected.
`action`	Yes	create \| get \| list \| update \| delete
`confirm`	No	Set to true ONLY after the user has reviewed the plan returned by a previous call with status 'confirmation_required'. Required for destructive/security-sensitive actions.
`dry_run`	No	If true, validate and return the planned change without executing it.
`options`	No	Connection options, e.g. {host, port, user, password} (Snowflake also sfWarehouse...). Required for create and update. Secret values are never returned.
`page_size`	No	Max items to return (server caps this).
`page_token`	No	next_page_token from a previous response.
`connection_type`	No	create only: AWS_SECRETS_MANAGER, AZURE_KEY_VAULT, BIGQUERY, CONFLUENCE, DATABRICKS, DYNAMICS365, GA4_RAW_DATA, GITHUB, GLUE, HIVE_METASTORE, HTTP, HUBSPOT, JDBC, META_MARKETING, MYSQL, NETSUITE, ORACLE, OUTLOOK, POSTGRESQL, POWER_BI, REDSHIFT, SALESFORCE, SALESFORCE_DATA_CLOUD, SERVICENOW, SMARTSHEET, SNOWFLAKE, SQLDW, SQLSERVER, TERADATA, TIKTOK_ADS, WORKDAY_RAAS, ZENDESK

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`page`	No
`plan`	No
`tool`	Yes
`action`	No
`safety`	No
`status`	No		success
`summary`	Yes
`warnings`	No
`next_steps`	No	Suggested follow-up calls.
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavioral detail beyond annotations: create/update requirements, update replacing the full options map, secrets never being returned, and per-action safety classifications (READ_ONLY, SECURITY_SENSITIVE, DESTRUCTIVE). This is exactly the kind of context an agent needs for a multi-action, security-sensitive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and connection types, then action requirements, then security context. Dense and useful, though the safety classification sentence partially repeats the preceding SECURITY_SENSITIVE/DESTRUCTIVE statement.

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

Completeness5/5

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

For a 9-parameter, multi-action tool with an output schema, the description covers the critical call-time requirements, secret handling, destructive behavior, and per-action safety. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, but the description adds cross-parameter semantics: which fields are required per action, how spec relates to options, and that update replaces the options map. This goes beyond the schema's field-level descriptions.

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?

States a specific verb and resource: managing Unity Catalog Lakehouse Federation connections, with examples of supported connection types. Distinguishes this tool from the many other manage_uc_* siblings by naming the specific resource domain.

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?

Clearly explains what each action does and the required parameters for create/update, giving strong action-level usage context. It does not explicitly name alternatives or when-not-to-use this tool versus sibling connection-related tools, so it falls short of a 5.

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

Deploy Server