sigma-streaming-platform-mcp

list_error_channels

Get a quick overview of all channels in error state for a specific application. Identify and debug streaming issues efficiently.

Instructions

List all channels currently in error state for an app UUID. Quick debugging overview.

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": {
      "appUuid": "<appUuid>"
    },
    "name": "list_error_channels"
  }
}

Input Schema

Name	Required	Description	Default
`appUuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 28, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Describes the read-only nature (listing channels) but lacks details about error state definition, output format, or potential side effects. Adequate for a simple list, but could be more transparent about return data.

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?

Two sentences, no redundancy. Front-loaded with the verb and resource. Every word contributes 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 simple list tool with one param and no output schema, the description is fairly complete. It conveys purpose and scope. Could benefit from mentioning the output structure or any pagination, but given the 'quick overview' intent, it's acceptable.

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 only parameter (appUuid) is mentioned in the description as 'for an app UUID,' providing context. However, with 0% schema description coverage, the description should be more explicit about the UUID format or constraints. It compensates partially but not fully.

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?

Clearly states the action (list), the resource (channels in error state), and the scope (for a specific app UUID). Distinguishes from sibling 'list_channels' by specifying the error state filter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes as 'quick debugging overview,' indicating when to use for debugging. While it doesn't explicitly state when not to use, the context of siblings like 'list_channels' provides implicit guidance. No alternatives mentioned.

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

Deploy Server