Skip to main content
Glama
Sign In
mcp-fabric-api

mcp-fabric-api

by mkoziel2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eventstream_delete

Destructive

Remove an eventstream from a Microsoft Fabric workspace. Provide the workspace ID and eventstream ID to delete the specified eventstream.

Instructions

Delete an eventstream

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": {
      "workspaceId": "<workspaceId>",
      "eventstreamId": "<eventstreamId>"
    },
    "name": "eventstream_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesThe workspace ID
eventstreamIdYesThe eventstream ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, and the description is consistent with them by stating deletion. However, it adds no further behavioral context such as irreversibility, effect on dependent resources, or required permissions.

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?

A single, clear sentence with no filler. It front-loads the action and resource and every word contributes to the meaning.

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 two-parameter deletion with explicit annotations, this is arguably sufficient to invoke, but it lacks any description of side effects or the expected outcome. There is also no output schema to clarify what a successful deletion returns.

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?

Both parameters are already fully described in the input schema (workspaceId and eventstreamId), so the description is not required to repeat them. It adds no semantic detail about how to obtain or format the IDs.

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

Purpose4/5

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

The description clearly states a specific action and resource: deleting an eventstream. It is unambiguous within the eventstream sibling group, though it offers no detail about the deletion scope or what distinguishes it from other eventstream operations beyond the verb.

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?

There is no guidance about when to use this tool instead of alternatives or any exclusions/prerequisites. The intended usage is implied by the verb 'delete' but not explicitly connected to a scenario such as removing an unneeded eventstream.

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