Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Delete Stream

delete_stream

Delete a stream from a specified runbook by providing the runbook ID and stream ID, removing that stream from the runbook's workflow.

Instructions

Delete a stream from a runbook.

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": {
      "runbook_id": "<runbook_id>",
      "stream_id": "<stream_id>"
    },
    "name": "delete_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesThe ID of the stream to delete.
runbook_idYesThe ID of the runbook containing the stream.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the entire behavioral burden and does not meet it: it never states whether deletion is permanent or reversible, what happens to tasks or data inside the stream, or what permissions are required. For a destructive mutation, these omissions matter far more than for a read operation.

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?

A single short sentence that is front-loaded with the verb and resource, with zero filler. It is efficient rather than padded; the weakness is under-specification, not verbosity.

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?

An output schema exists, so return values need not be explained, and the two required parameters are fully covered by the schema. However, for an unannotated destructive tool the description should at minimum convey irreversibility or side effects, which it does not.

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%, so both runbook_id and stream_id are already documented in the schema. The phrase "from a runbook" adds a light containment cue, but no format, sourcing, or ID-discovery guidance beyond what the schema provides, so the baseline of 3 applies.

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 names a specific verb and resource ("Delete a stream") plus its container ("from a runbook"), which clearly separates it from siblings like create_stream, get_stream, and update_stream. It does not explicitly contrast itself with any alternative, but the operation is unambiguous.

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 on when to use this tool versus alternatives, no preconditions (e.g., does the stream need to be empty, does it require a specific permission level), and no exclusions. The agent is left to infer everything about appropriate invocation from the name alone.

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