Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Update Stream

update_stream

Modify an existing stream in a runbook by updating its name, color, or description.

Instructions

Update an existing stream 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>",
      "stream_id": "<stream_id>"
    },
    "name": "update_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new name for the stream.
colorNoThe new color for the stream in CSS-friendly format.
stream_idYesThe ID of the stream to update.
runbook_idYesThe ID of the runbook containing the stream.
descriptionNoThe new description for the stream.

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 behavioral burden for a mutation. It does not state whether the update is partial (are omitted or null fields preserved?), whether changes are reversible, what permissions are required, or what happens on an unknown stream_id - all critical for a write 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 with no wasted words, and the resource being mutated is front-loaded. It is efficient, though thin for a five-parameter mutation tool.

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?

Output schema exists so return values need not be explained, but for a mutating tool with zero annotation coverage the description should clarify partial-update semantics and any permission or validation behavior. It omits all of that, leaving an agent unable to predict the effect of sending nulls.

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 every parameter (name, color, description, stream_id, runbook_id) is already documented in the schema, including the CSS format note for color. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 states a specific verb and resource ('Update an existing stream') and names the parent context ('in a runbook'). It is clear what the tool operates on, but it never distinguishes itself from the sibling operations create_stream, delete_stream or get_stream.

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 choose this tool over create_stream or delete_stream, and no prerequisites such as required permissions or the need for an existing stream ID. The agent is left to infer the usage context 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.