mcp-fabric-api

eventstream_list

Read-only

Retrieve a complete list of eventstreams in a workspace by providing its workspace ID.

Instructions

List all eventstreams in a workspace

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>"
    },
    "name": "eventstream_list"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the scoping behavior ('all ... in a workspace'), but it does not disclose return format, ordering, pagination, or whether full definitions are included. This adds minimal context beyond what annotations and schema already convey.

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, front-loaded sentence with no filler or redundancy. It is appropriately sized for a simple list operation and every word contributes to meaning.

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?

For a read-only list tool with one well-documented parameter and no output schema, the description is largely complete: it names the action, resource, and scope. Minor gaps exist around return type, pagination, and routing to alternatives, but they do not seriously hinder correct invocation.

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 workspaceId parameter already has a description ('The workspace ID'). The description's 'in a workspace' reinforces the parameter's role but provides no additional semantic detail beyond the schema.

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 uses a specific verb ('List'), a clear resource ('eventstreams'), and scope ('in a workspace'), making the operation unambiguous. It is easily distinguished from eventstream_get and other resource-specific list tools by the resource name and action.

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?

The description implies when to use the tool (when you need to list all eventstreams in a workspace) but provides no explicit guidance on alternatives or when not to use it. It does not mention eventstream_get for a single eventstream or eventstream_get_definition for full definition details.

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

Deploy Server