Skip to main content
Glama

Feature Library

Read a playbook

get_playbook
Read-only

Free. The library’s playbooks: how parts are placed, moved, made accessible and kept fast, with the reason for every rule and a checklist. Without an id, the list (title, summary, the parts each covers); with an id, the playbook in full as markdown. get_kit and get_recipe name the playbooks that cover their parts: read those (playbooks) before wiring the parts; the ones under playbooksIfUsed only when the build uses that part or does that work.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional: the playbook id, e.g. placement or accessibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new context by disclosing the dual return mode (summary list vs. full markdown) and even the list fields (title, summary, parts covered), plus that the call is 'Free'. It does not indicate how large a full playbook is or whether output is paginated, which for a markdown-returning tool would matter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and information-dense, but the second half is a single sprawling sentence stacking three conditionals, and the bare field name 'playbooksIfUsed' appears without explanation of where it comes from. 'Free.' is a useful but oddly isolated opener. Content mostly earns its place; the structure does not.

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-optional-parameter read tool with no output schema, this covers mode switching, content of the response, and sequencing relative to the kit/recipe tools. The remaining gap is scale and format detail of the full-markdown case, which is minor given the annotations already establish a safe, closed read.

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% and the schema already gives example ids, so the baseline is 3. The description goes further by explaining what omitting the id does versus supplying one, which is the single most important semantic fact about this parameter and is not encoded in the schema itself.

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?

The description names a specific resource (the library's playbooks) and states exactly what they contain: how parts are placed, moved, made accessible and kept fast, plus reasons and checklists. It also distinguishes the two operating modes (list without an id, full markdown with an id), so an agent can tell this apart from get_kit/get_recipe without opening any schema.

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?

It gives explicit ordering guidance: get_kit and get_recipe name the covering playbooks, and those should be read before wiring parts, with playbooksIfUsed entries deferred until the build actually uses that part or does that work. That is real when-to-use instruction tied to siblings, though the run-on phrasing makes the conditional ('only when the build uses that part') harder to parse than it needs to be, and there is no explicit when-not-to-call statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources