Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Runbook Template Copies

get_runbook_template_copies

Find all runbooks created from a specific runbook template by passing the template runbook ID.

Instructions

Get all runbooks that were created from a specific runbook template.

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_template_copies"
  }
}

Input Schema

NameRequiredDescriptionDefault
runbook_idYesThe template runbook ID to find copies of.

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

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden, and the word 'Get' is the only signal that this is a read-only operation. It says nothing about result volume, pagination, ordering, or whether archived/deleted copies are included — meaningful gaps for an 'all' query. An output schema exists, so omitting return-field detail is acceptable, but the behavioral profile is thin.

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 sentence with no filler, and the scoping concept (copies of a template) is front-loaded. It is efficient but very sparse — a short clause on ordering or scope would earn its place given the absence of annotations.

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 read tool with a fully documented schema and an output schema, the description covers the essential contract: what it returns and against which ID. The remaining gap is behavioral (pagination/scope of 'all'), which is minor relative to the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines runbook_id as the template runbook ID to find copies of. The description restates that framing ('specific runbook template') but adds no extra meaning, so the baseline of 3 applies.

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 gives a specific verb and resource ('Get all runbooks that were created from a specific runbook template'), which is enough to distinguish this from get_runbook_by_id (single runbook) or get_runbook_tasks (tasks of a runbook). It stops short of explicitly naming a sibling or the template-vs-instance distinction as a routing cue, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent must infer that this tool applies when it holds a template runbook ID and wants the derived copies. There is no explicit when-to-use statement, no when-not, and no named alternative such as get_runbook_by_id for looking up the template itself.

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