Book Guide MCP

by Kayforkind

Overview Schema Source Related Servers Discussions Admin

Python

Local

skill_playbook_start

Start a multi-step playbook session from a book guide, receiving the first step's instructions and a unique session ID.

Instructions

Start a multi-step playbook session (L2). Returns step 0 instructions and session_id.

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": {
      "book_id": "<book_id>",
      "playbook_id": "<playbook_id>"
    },
    "name": "skill_playbook_start"
  }
}

Input Schema

Name	Required	Description	Default
`book_id`	Yes	Skill id.
`playbook_id`	Yes	Playbook id from skill_playbook_list.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate non-read-only and non-idempotent behavior. Description adds that it returns step 0 and session_id, and mentions multi-step nature, but does not elaborate on side effects, permissions, or state changes.

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

Conciseness5/5

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

Single sentence, 12 words, front-loaded with key information (start, multi-step, returns). No waste.

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?

With output schema present, return details are covered. All parameters described. Could benefit from clarifying what a playbook session is or prerequisites, but sufficient for a simple starter tool.

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?

Schema description coverage is 100%, so baseline is 3. Description does not add additional meaning beyond schema descriptions for the two parameters.

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?

Description clearly states verb 'start', resource 'multi-step playbook session', and specifies return value (step 0 instructions and session_id). Distinguishes from siblings like skill_playbook_list and skill_playbook_next.

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?

Implied usage as the starting point for a playbook session, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or prerequisites.

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