Skip to main content
Glama
Sign In
Microsoft Fabric MCP Server

Microsoft Fabric MCP Server

by og-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fabric_delete_eventhouse

Destructive

Remove an eventhouse from a Fabric workspace by providing its item ID. This action is destructive and permanently deletes the target eventhouse.

Instructions

Delete an eventhouse. Destructive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "fabric_delete_eventhouse"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem ID
workspaceNoWorkspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The annotation already provides destructiveHint: true, so the 'Destructive.' adds no new information. The description does not disclose additional behavioral traits like irreversibility or cascading effects beyond what the annotation implies.

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 extremely concise: two sentences with no wasted words. Every sentence earns its place.

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

Completeness3/5

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

For a simple delete operation with two parameters and existing annotations, the description is adequate but could mention that deletion is permanent or provide return behavior. It is minimally complete.

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 100%, and the description does not add any meaning beyond the schema's field descriptions. Baseline score of 3 applies.

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 'Delete an eventhouse' with a specific verb and resource. It distinguishes from sibling tools like fabric_delete_dataflow or fabric_delete_eventstream by naming the resource type.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as fabric_delete_item or other delete tools. No prerequisites or conditions mentioned.

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

Deploy Server

Other Tools