sigma-streaming-platform-mcp

stop_channel

Stops a transcoding channel by supplying its app UUID and channel ID.

Instructions

Stop a transcoding channel. appUuid must be the app UUID.

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

Input Schema

Name	Required	Description	Default
`appUuid`	Yes
`channelId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, idempotency, required permissions, or what happens if the channel is already stopped. The description is minimal and does not compensate for the lack of 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?

The description is very concise at two sentences with no unnecessary information. However, the second sentence is somewhat redundant if the parameter name already implies a UUID, but it does not detract significantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 required params, no output schema, no annotations), the description is incomplete. It lacks information on return values, error scenarios, success criteria, or any behavioral context that would help an agent use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only adds minimal value by restating that appUuid must be the app UUID. It does not explain the parameter's role or any constraints beyond the schema's required field.

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 clearly states the action ('Stop') and the resource ('a transcoding channel'), which is specific and distinguishes it from sibling tools like start_channel and restart_channel.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no context for usage. The only note is a parameter requirement ('appUuid must be the app UUID'), which is more about semantics than usage guidelines.

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

Deploy Server