Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Streams

list_streams

Retrieves all streams and substreams for a specified runbook, with an option to include computed forecast fields for scheduling visibility.

Instructions

List all streams for a specific runbook, including substreams.

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": "list_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
forecastNoIf true, returns computed forecast fields (start_display, end_display, etc.).
runbook_idYesThe ID of the runbook to list streams for.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYesTop-level metadata for a list response.
linksYesPagination links for a list response.
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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. It does disclose one genuinely useful trait – that substreams are returned alongside streams – but says nothing about pagination, result ordering, permissions required, or behaviour when the runbook ID is invalid.

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?

A single sentence with zero filler, front-loading the action and resource before the scoping and inclusion clauses. Nothing could be removed without losing information.

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 two-parameter read tool with a fully documented schema and an output schema, the description covers purpose, scope and the substreams inclusion rule. The remaining gap is operational detail such as pagination and error behaviour, which is minor given the low complexity.

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 parameters are already documented in the schema; the baseline is 3. The description adds nothing about the forecast flag or how runbook_id scoping affects results, so no credit above baseline.

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 ('List all streams') plus the scoping constraint ('for a specific runbook') and an inclusion rule ('including substreams'). It is clearly distinguishable from create_stream, delete_stream and get_stream, though it never names them.

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?

The description gives no explicit when-to-use guidance, no prerequisites, and no mention of when to prefer get_stream for a single stream or how to page through results. Usage must be inferred entirely from the name and the runbook scoping clause.

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