Skip to main content
Glama

Read one waste runbook

get_playbook
Read-onlyIdempotent

Fetch step-by-step runbooks for a named cloud waste pattern, including symptoms, detection queries, fixes, and anti-patterns. Use it to detect, confirm, or fix that pattern.

Instructions

Fetch the step-by-step runbook for one specific waste pattern: symptoms, the detection queries to run, the fix, and the anti-pattern to avoid.

Use this when the user asks how to detect, confirm, or fix one specific
named waste pattern (zombie NAT gateway, snapshot sprawl, idle SageMaker
endpoint, ...), including questions about the user's own resources
("which of my X..."). Each runbook includes a detection query the user
can run in their own cloud account; this connector has no access to the
user's accounts.

Args:
    name: Playbook slug as returned by ``list_playbooks`` (e.g.
        ``"aws-zombie-nat-gateway"``, ``"azure-orphan-disks"``,
        ``"cross-cloud-untagged-spend-drift"``).

Returns ``{"name": ..., "title": ..., "content": "...", "lines": N}``.
On miss, returns ``{"error": ..., "suggestions": [...]}`` with up to
three string-distance matches so the caller can self-correct.

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": {
      "name": "<name>"
    },
    "name": "get_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a meaningful constraint: the connector has no access to the user's accounts, so detection queries are handed to the user rather than executed. It also describes the miss path with up to three fuzzy suggestions, which changes how a caller should recover from an error. Minor gap: no note on content size limits despite a "lines" count and no access restrictions discussed.

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 purpose, then usage, then an Args/Returns block that is easy to scan. The parenthetical example list is slightly padded, but every section maps to real caller needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-parameter, read-only tool with an output schema and rich annotations — the remaining burden is exactly what the description covers: what the resource is, when to reach for it, what the argument means, and what the error shape looks like.

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

Parameters5/5

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

The schema gives the sole parameter zero description (0% coverage), so the description carries the full burden and does: it defines `name` as a playbook slug as returned by list_playbooks and supplies three concrete example slugs across AWS, Azure, and cross-cloud patterns. That is enough to construct a valid call without guessing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch the step-by-step runbook for one specific waste pattern") and immediately enumerates the contents (symptoms, detection queries, fix, anti-pattern). This is clearly distinguishable from list_playbooks/find_playbooks, which don't return the runbook body.

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?

Gives an explicit trigger: the user asks how to detect, confirm, or fix one specific named waste pattern, including "which of my X" questions. It also implies the slug comes from list_playbooks, but it does not name the search-style siblings (find_playbooks) as the path when the pattern name isn't already known.

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