Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Runbook Teams

get_runbook_teams

Fetch all teams linked to a runbook using its runbook ID to identify involved teams and coordinate ownership or access.

Instructions

Get all teams associated with 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>"
    },
    "name": "get_runbook_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
runbook_idYesThe runbook ID to fetch teams for.

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations provided, the description carries the full behavioral burden. It does disclose that this is a bulk read ('all teams') scoped to a single runbook, and the presence of an output schema means return shape needn't be explained. However, it says nothing about permission requirements, behavior for an unknown runbook_id, or whether results are paginated.

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 filler, which is well matched to a simple one-parameter read. It is efficient, though it borders on under-specification rather than demonstrating tight partitioning of 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 simple read with one fully documented required parameter and an output schema, the definition covers what the tool does and what it operates on. The only meaningful gap is the absence of annotations, which leaves read-only semantics and error behavior implied rather than stated.

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 schema already documents runbook_id at 100% coverage with a description ('The runbook ID to fetch teams for'), so the baseline is 3. The description adds no further meaning about the identifier's format, source, or any filtering behavior beyond what the schema states.

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: 'Get all teams associated with a runbook.' An agent can immediately tell this retrieves team associations scoped to a single runbook, which distinguishes it in kind from siblings like get_runbook_by_id or get_runbook_tasks. It stops short of naming any sibling or contrasting its scope, so it is clear but not sibling-differentiating.

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 when-to-use guidance, no stated preconditions, and no mention of alternatives. The agent must infer that this is the tool for listing teams attached to a runbook rather than looking them up some other way. Nothing indicates when this call would be inappropriate or what to do if the runbook has no teams.

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