dbx-mcp

Genie spaces

manage_genie

Destructive

Create, update, inspect, or delete AI/BI Genie spaces for natural-language-to-SQL over Unity Catalog tables, and manage their conversations and messages.

Instructions

Manage AI/BI Genie spaces (natural-language-to-SQL over Unity Catalog tables).

Actions:

list / get (include_serialized_space for the full definition).
create: spec = {warehouse_id, serialized_space (JSON string or object), title, description, parent_path}. Tip: get an existing space with include_serialized_space=true to see the serialized_space format.
update: spec with any of title, description, warehouse_id, parent_path, serialized_space (full replacement), etag.
delete: move the space to trash (requires confirm).
list_conversations / list_messages (conversation_id) / delete_conversation (requires confirm). Use ask_genie to ask questions.

Safety classification: list, get, list_conversations, list_messages = READ_ONLY; create, update = WRITE; delete, delete_conversation = DESTRUCTIVE.

Input Schema

TableJSON Schema

Name	Required	Description
`spec`	No	Request body fields for create/update, using the Databricks REST API field names (snake_case). Unknown fields are rejected.
`action`	Yes	Operation to perform.
`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.
`space_id`	No	Genie space id (all actions except list/create).
`page_size`	No	Max items to return (server caps this).
`page_token`	No	next_page_token from a previous response.
`include_all`	No	list_conversations: include all users' conversations (requires CAN MANAGE).
`conversation_id`	No	Conversation id for list_messages/delete_conversation.
`include_serialized_space`	No	get: include the serialized space definition (requires CAN EDIT).

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.9/5.0

Behavior5/5

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

Goes well beyond the annotations by classifying each action as READ_ONLY/WRITE/DESTRUCTIVE, disclosing that delete moves to trash, that update's serialized_space is a full replacement, that etag is used for concurrency, that list_conversations requires CAN MANAGE and include_serialized_space requires CAN EDIT, and the two-step confirm flow.

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?

Front-loads the resource scope, then uses a tight per-action list plus a safety classification line. Every line carries decision-relevant information; nothing is padding.

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 an 8-action, 10-parameter tool with an output schema and annotations, the description supplies the action semantics, safety tiers, confirmation protocol, and permissions that structured fields alone would not convey. Nothing an agent needs to select or invoke it correctly 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 coverage is already 100%, but the description adds action-to-parameter mapping that the schema does not carry: which spec fields apply to create vs update, that etag belongs to update, and that include_serialized_space is a get-only flag. Useful, though individual parameter meanings largely remain in the schema.

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+resource (manage AI/BI Genie spaces) and immediately scopes it as natural-language-to-SQL over Unity Catalog tables. It enumerates every action, so an agent can tell it apart from ask_genie and the other manage_* siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes query-asking to ask_genie, tells the agent which actions need confirm, and gives a concrete tip (fetch include_serialized_space=true first to learn the spec format). Usage conditions are stated, not implied.

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

Deploy Server