Skip to main content
Glama
microsoft

Microsoft Fabric RTI MCP Server

Official
by microsoft

eventstream_create

Destructive

Create an Eventstream in Microsoft Fabric for real-time data ingestion. Auto-generates IDs, name, and definition, or accept custom configuration.

Instructions

Create an Eventstream item in Microsoft Fabric.
Authentication is handled transparently using Azure Identity.

User-friendly options:
- Provide only eventstream_name: Auto-generates IDs and creates basic eventstream
- Provide only eventstream_id: Auto-generates name as "Eventstream_YYYYMMDD_HHMMSS"
- Provide both: Uses your specified values
- Provide full definition: Advanced users can specify complete eventstream config

:param workspace_id: The workspace ID (UUID)
:param eventstream_name: Name for the new eventstream (auto-generated if not provided)
:param eventstream_id: ID for the eventstream (auto-generated if not provided)
:param definition: Eventstream definition (auto-generated basic one if not provided)
:param description: Optional description for the eventstream
:return: Created eventstream details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYes
eventstream_nameNo
eventstream_idNo
definitionNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already show destructiveHint=true; description adds context on transparent authentication via Azure Identity and auto-generation behavior for IDs and names. Does not cover failure modes or idempotency, but adds meaningful detail beyond annotations.

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-structured with bullet points and front-loaded purpose. Every sentence adds value, though slightly verbose with repeated option explanations. Could be more succinct but is clear.

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 params, destructive action) and presence of an output schema, the description covers creation scenarios adequately. Missing details on error handling and parameter constraints, but sufficient for basic usage.

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?

With 0% schema description coverage, the description fully explains all 5 parameters including auto-generation rules for eventstream_name, eventstream_id, and definition. Provides clear, actionable semantics for each parameter.

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?

Description clearly states 'Create an Eventstream item in Microsoft Fabric' with specific verb and resource. Distinguishes from sibling eventstream_create_from_definition by outlining auto-generation vs full definition options.

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?

Describes four usage patterns (name only, ID only, both, full definition) but does not explicitly compare with sibling tools like eventstream_create_from_definition, leaving when-to-use somewhat implied.

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/microsoft/fabric-rti-mcp'

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