Microsoft Fabric MCP Server

fabric_create_eventhouse

Create an eventhouse in Microsoft Fabric with a required display name and optional description and workspace ID.

Instructions

Create an eventhouse.

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": {
      "displayName": "<displayName>"
    },
    "name": "fabric_create_eventhouse"
  }
}

Input Schema

Name	Required	Description
`displayName`	Yes
`description`	No
`workspace`	No	Workspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.1/5.0

Behavior1/5

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

With no annotations present, the description carries the full burden of disclosing behavioral traits. The single sentence 'Create an eventhouse' reveals no information about idempotency, permissions, side effects, or what happens if the eventhouse already exists, leaving the agent completely in the dark.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise. However, it is under-specified and lacks essential details; brevity comes at the cost of clarity. It earns a score of 3 because it is not verbose, but it does not provide sufficient information.

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

Completeness1/5

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

Given the tool's complexity (3 parameters, no output schema, many siblings, no annotations), the description is severely incomplete. It does not explain what an eventhouse is, how parameters affect creation, or how this tool differs from similiar create tools. The agent cannot make informed decisions based on this description.

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

Parameters2/5

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

Schema coverage is only 33%—only the 'workspace' parameter has a description. The tool description does not explain any of the three parameters (displayName, description, workspace) beyond what little the schema provides. Since coverage is low, the description should compensate but fails to do so.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create an eventhouse,' which specifies a verb and resource. However, it lacks context about what an eventhouse is, and does not differentiate this tool from sibling create tools like fabric_create_lakehouse or fabric_create_kql_database, leaving the purpose vague.

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 is provided on when to use this tool versus alternatives such as fabric_create_kql_database or fabric_create_lakehouse. The description does not mention prerequisites, target users, or scenarios, offering no help in tool selection.

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

Deploy Server