Skip to main content
Glama
sdebruyn

fabric-dw-mcp-cli

by sdebruyn

drop_column_mask

Remove a dynamic data mask from a column to expose its original values. This operation permanently removes protection and cannot be undone.

Instructions

Remove a dynamic data mask from a column.

Executes ALTER TABLE ... ALTER COLUMN ... DROP MASKED. This is a permanently destructive operation -- the mask is removed from the column and unmasked values become visible to all users who query the column. Requires FABRIC_MCP_ALLOW_DESTRUCTIVE=1.

Args: workspace: Workspace name or GUID. item: Warehouse or SQL endpoint name or GUID. table_schema: Schema name of the target table. table_name: Name of the target table. column_name: Name of the column whose mask to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
workspaceYes
table_nameYes
column_nameYes
table_schemaYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries full burden. It clearly labels the operation as 'permanently destructive' and warns that unmasked values become visible. It also notes the environment variable requirement. This is good transparency for a destructive tool.

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?

The description is concise with a clear purpose sentence, followed by the SQL invocation, destructive warning, requirement, and parameter list. Every sentence adds value without redundancy. Front-loaded with the most important info.

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?

Given the complexity (5 required params, destructive operation, no annotations), the description covers the essential behavior and prerequisites. It does not explain return values, but an output schema exists. Missing details like error conditions are acceptable for this level of detail.

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 0%, so the description must compensate. It lists each parameter with brief clarification (e.g., 'Workspace name or GUID', 'Warehouse or SQL endpoint name or GUID'). This adds minor meaning beyond the schema titles, but does not explain constraints or formats.

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 explicitly states 'Remove a dynamic data mask from a column,' which is a specific verb and resource. It clearly distinguishes from sibling tools like set_column_mask (sets a mask) and list_masked_columns (lists masks).

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?

The description mentions the underlying SQL command and requires FABRIC_MCP_ALLOW_DESTRUCTIVE=1, but does not explicitly state when to use this tool versus alternatives like set_column_mask. Usage context is implied but not directly guided.

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