Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Stream

get_stream

Retrieve details for a specific stream or substream in a Cutover runbook using its runbook ID and stream ID.

Instructions

Get details of a specific 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>",
      "stream_id": "<stream_id>"
    },
    "name": "get_stream"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYes
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden, but 'Get' clearly implies a non-mutating read and an output schema exists to cover return values. It adds nothing about permissions, what happens for substreams versus streams, or error behavior when the stream is absent, which is the main behavioral 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 no wasted words, appropriately sized for a simple retrieval tool. It is efficient but so terse that the structure carries no additional routing or scoping 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 full schema coverage and an output schema, the description covers what is needed to call it correctly. It falls short only on the substream-versus-stream distinction and on guidance relative to list_streams, which are minor for a simple getter.

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 coverage is 100% with both parameters fully documented, so the baseline is 3. The description adds only the mild notion that a stream lives inside a runbook and may be a substream, which loosely corroborates the two required IDs without adding format or lookup detail.

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 ('Get details of a specific stream or substream in a runbook'), which is unambiguous about the operation. It does not distinguish itself from siblings like list_streams or get_runbook_by_id, so an agent must infer the single-item vs list distinction from the name alone.

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 instead of list_streams or how a stream is identified relative to a runbook. The description offers no context, exclusions, or alternatives, leaving the agent to infer usage from the tool name and required parameters.

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