Skip to main content
Glama
sdebruyn

fabric-dw-mcp-cli

by sdebruyn

create_empty_table

Create an empty table in a Fabric Data Warehouse by defining columns with names and T-SQL types. Specify schema, table name, column definitions, and optional clustering.

Instructions

Create an empty table from an explicit column spec (DDL only, no data).

Builds CREATE TABLE [schema].[table] (col TYPE [NULL|NOT NULL], …) from the supplied column definitions. No data is read or inserted; this is a pure DDL operation.

Server-side file access is unreliable in MCP deployments, so CSV/Parquet inference is not available via this tool — use the fabric-dw tables create --from-parquet or --from-csv CLI commands instead.

Only supported on Fabric Data Warehouses (not SQL Analytics Endpoints).

When cluster_by is supplied, each column must appear in columns.

Args: workspace: Workspace name or GUID. item: Warehouse name or GUID. qualified_name: Dot-separated qualified table name, e.g. dbo.sales. columns: List of column definitions, each a dict with: name (str) — column identifier; sql_type (str) — Fabric-DW T-SQL type, e.g. "INT", "VARCHAR(255)"; nullable (bool, optional, default true) — whether the column allows NULL. cluster_by: Optional list of column names for the CLUSTER BY clause (up to 4). Each name must appear in columns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
columnsYes
workspaceYes
cluster_byNo
qualified_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses it is pure DDL, no data read/inserted, and mentions limitations about file access and supported environments.

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?

The description is well-structured with a summary, explanatory paragraphs, and an Args list, but is somewhat lengthy; every sentence adds value, though slight trimming could improve conciseness.

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?

Given the tool's complexity, the description covers all essential aspects: purpose, parameters, constraints, usage guidance, alternatives, and environment restrictions. Output schema exists, so return values do not need explanation.

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

Parameters5/5

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

Despite 0% schema coverage, the description explains each parameter in detail, including the structure of columns with sub-fields (name, sql_type, nullable) and the constraint that cluster_by columns must appear in columns.

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 it creates an empty table using DDL only, distinguishing it from siblings like create_table or clone_table by emphasizing no data is involved.

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 notes that server-side file inference is unavailable and directs to CLI alternatives; also specifies it is only for Fabric Data Warehouses, not SQL Analytics Endpoints, and provides constraints on cluster_by.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sdebruyn/fabric-dw-mcp-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server