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

mcp-fabric-api

by mkoziel2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eventstream_get

Read-only

Retrieve detailed information about a specific Microsoft Fabric eventstream by providing workspace and eventstream IDs.

Instructions

Get details of a specific 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_get"
  }
}

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 declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no extra behavioral context beyond 'get details', such as return format, permissions, or failure behavior, but it also does not contradict the annotations.

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 a single concise sentence with no filler. It front-loads the operation and is immediately understandable.

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 read-only get operation with fully documented parameters, the description is nearly sufficient. However, with no output schema and a sibling eventstream_get_definition, the term 'details' is underspecified and could lead to choosing the wrong tool.

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?

The schema describes both parameters (workspaceId and eventstreamId) with 100% coverage, so the description does not need to repeat them. The description adds no parameter-level detail beyond what the schema already provides, making the baseline 3 appropriate.

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 states a clear verb ('Get') and a specific resource ('a specific eventstream'), so the core action is obvious. However, it does not distinguish itself from the similarly named sibling eventstream_get_definition, leaving some ambiguity about whether 'details' means metadata or definition.

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 versus alternatives like eventstream_list or eventstream_get_definition. The word 'specific' weakly implies an ID-based lookup, but the description does not state exclusions or selection criteria.

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