Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Create Stream

create_stream

Creates a new stream or substream in a Cutover runbook, letting users assign a name, optional description, color, and parent stream ID.

Instructions

Create a new stream or substream in 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>",
      "name": "<name>"
    },
    "name": "create_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the new stream.
colorNoThe color assigned to the stream in CSS-friendly format (e.g., "#f0f0f0" or "rgb(0,0,0)").
runbook_idYesThe ID of the runbook to create the stream in.
descriptionNoAn optional description for the stream.
parent_stream_idNoThe ID of the parent stream if creating a substream.

Output Schema

NameRequiredDescriptionDefault
dataYes
includedNo

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?

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It mentions the substream case but says nothing about permissions needed, whether the new stream is returned or just its ID, name-uniqueness behavior, or what happens to ordering/positioning in the runbook. For a mutation tool this is a meaningful gap.

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 front-loaded sentence with zero waste and no ambiguity. It is efficient, though its brevity borders on under-specification for a mutation tool.

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 flat five-parameter schema is complete. What remains missing is the behavioral context a write operation needs with no annotations, particularly authorization requirements and any side effects.

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 all five parameters including parent_stream_id and color are already fully documented in the schema. The description's phrase 'or substream' lightly signals the parent_stream_id case but adds no syntax, format, or constraint detail beyond the schema.

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?

States a specific verb and resource (create a stream or substream in a runbook) and covers both the top-level and nested case. It is clearly distinguishable from update_stream and delete_stream by the verb alone, though it never names those siblings explicitly.

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 when-to-use, when-not-to-use, or alternative guidance is given. The agent must infer from the verb that this is the creation path versus update_stream, and nothing states prerequisites such as required role or whether the runbook must be in a particular state.

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