Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Runbook By Id

get_runbook_by_id

Retrieve a Cutover runbook's details by its unique ID to review its configuration and related cutover information.

Instructions

Fetch details for a specific runbook by its ID.

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

Input Schema

NameRequiredDescriptionDefault
runbook_idYesThe unique identifier for the runbook.

Output Schema

NameRequiredDescriptionDefault
dataYes
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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, yet it only restates the name. It does not disclose what happens with an unknown or invalid ID, whether deleted or archived runbooks are still retrievable, or whether the call is a side-effect-free read — all relevant to a lookup tool with zero structured hints.

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, front-loaded sentence with no wasted wording. Brevity is appropriate for the tool's simplicity, though the one sentence could carry slightly more value without bloat.

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 one-parameter lookup with an output schema (which already defines the returned detail structure) and complete schema coverage, the essentials are present. What is missing is error/not-found behavior and a note on what fields the "details" comprise relative to sibling endpoints.

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?

The sole parameter is fully documented in the schema (100% coverage) including that it is the runbook's unique identifier and is required. The description adds no meaning beyond that, such as format or where to obtain the ID, so baseline 3 is appropriate.

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?

Clear specific verb ("fetch") and resource ("runbook") scoped to a single item by ID, which implicitly distinguishes it from list/get-children siblings such as get_runbook_tasks or get_runbook_teams. It stops short of naming alternatives or noting that this is the single-record counterpart to those tools, so it is clear but not sibling-differentiated.

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 versus other read tools (e.g., get_runbook_tasks for nested data) and no mention of prerequisites such as needing a valid runbook ID or any permission context. The agent must infer usage entirely from the name.

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