Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Query Runbook Types

query_runbook_types

Search runbook types by name, description, or capability flags to resolve the ID required for create_runbook.

Instructions

Find runbook types matching a name/description search and/or capability flags.

Use this to resolve a runbook type a user described in words into the id that create_runbook needs — e.g. "an incident runbook" (incident=True) or "a template with RTO/RTA enabled" (enable_rto=True). Every criterion is optional; passing none returns all usable runbook types. Multiple criteria are combined with AND.

Filtering is applied client-side over the full collection because the public API ignores query parameters on core/runbook_types.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_runbook_types"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive substring matched against the name, key and description.
dynamicNoWhen set, keep only types whose ``dynamic`` flag matches.
incidentNoWhen set, keep only types whose ``incident`` flag matches.
enable_rtoNoWhen set, keep only types whose ``enable_rto`` flag matches — these are the types supporting an RTO/RTA target.
include_archivedNoArchived types are excluded by default because they cannot be used for new runbooks. Set True to include them.
include_disabledNoDisabled types are excluded by default because they cannot be used for new runbooks. Set True to include them.
ai_create_enabledNoWhen set, keep only types whose ``ai_create_enabled`` flag matches.

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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that filtering happens client-side over the full collection because the upstream API ignores query parameters, which warns the agent about cost/result semantics. It also discloses that archived and disabled types are excluded by default and why. It does not mention auth requirements or read-only nature explicitly, and return shape is left to the output schema.

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?

Front-loaded with what the tool does, followed by the motivating use case, then the filtering caveat. Every sentence carries signal, though the double-backtick markup and doubled examples add slight visual noise. No filler or repetition of schema fields.

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 7-parameter, zero-required read tool with no annotations, the description covers purpose, triggering workflow, AND semantics, default exclusions, and the client-side filtering caveat. Return values are covered by the output schema, so nothing critical is missing. Only explicit read-only/authentication assurance and a named alternative are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: criteria are individually optional and combined with AND, and passing none is equivalent to listing everything usable. Minor mismatch: it describes the query as 'name/description search' while the schema also matches key, a small inconsistency that could confuse substring expectations.

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?

Names a specific verb and resource: 'Find runbook types matching a name/description search and/or capability flags.' That is clearly distinguishable from create_runbook or get_runbook_type_by_id. It never names list_runbook_types, however, and by saying 'passing none returns all usable runbook types' it partially overlaps with that sibling, leaving the boundary implicit.

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

Usage Guidelines4/5

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

Strong contextual guidance: it tells the agent this is the resolution step before create_runbook and gives concrete examples ('an incident runbook' → incident=True, 'a template with RTO/RTA enabled' → enable_rto=True). It also states that all criteria are optional and combined with AND. It stops short of explicit when-not guidance (e.g. 'if you already have the id, use get_runbook_type_by_id') and never names an alternative tool.

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