Skip to main content
Glama
sdebruyn

fabric-dw-mcp-cli

by sdebruyn

transfer_view

Move a SQL view to a different schema using ALTER SCHEMA TRANSFER, without rewriting the view's stored definition.

Instructions

Move a SQL view to another schema via ALTER SCHEMA ... TRANSFER OBJECT::....

Works on both Data Warehouses and SQL Analytics Endpoints — no DW-only guard is applied.

CAUTION: ALTER SCHEMA ... TRANSFER moves the view but does not rewrite the schema name inside the view's stored definition (sys.sql_modules.definition, OBJECT_DEFINITION()). After a transfer, the returned (and any subsequent get_view) definition may still show the old schema name in the CREATE ... AS header, even though the view now lives in the new schema. This tool does not rewrite the definition text — doing so would require parsing and regenerating SQL, which this project deliberately avoids.

Args: workspace: Workspace name or GUID. item: Warehouse or SQL endpoint name or GUID. qualified_name: Current dot-separated qualified view name, e.g. dbo.vw_sales. target_schema: Schema to move the view into, e.g. archive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
workspaceYes
target_schemaYes
qualified_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It explains the SQL statement used, notes the lack of definition rewrite, and warns about the side effect. Could mention permissions or idempotency, but still strong.

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?

Well-organized with clear purpose, scope, and caution. A bit verbose in the caution section but all sentences earn their place. Front-loaded with key action.

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?

Covers core behavior, SQL method, side effects, and environments. Missing error conditions, prerequisites (like ownership), and response description, but output schema exists. Almost complete for a mutation tool with side effects.

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?

Input schema has 0% description coverage, but the description provides explicit explanations for all 4 parameters with examples (qualified_name, target_schema), adding significant meaning beyond just property names.

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?

Clearly states the verb 'Move' and the resource 'SQL view', distinguishing it from siblings like transfer_table or transfer_function. Includes scope (both Data Warehouses and SQL Analytics Endpoints).

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?

Implied usage from name and siblings, but no explicit when-to-use or alternatives. Does not guide on when to prefer this over other transfer tools. Caution about definition rewrite is helpful but not a guideline.

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