kvm-pilot

doctrine

Read-onlyIdempotent

Re-serve bundled operating playbooks to re-anchor a session on written guidance. Call with no topic to list playbooks, or with one to get its full text.

Instructions

Re-serve the bundled operating doctrine (read-only; offline, no device I/O).

The skill's playbooks ship inside this package; this tool re-serves them so a session that never loaded the skill file — or has long since compacted it away — can re-anchor on the written doctrine instead of a faded memory of it. Call with no topic to list the topics; call with one for that playbook's full text. Read recovery the moment a host goes dark or a snapshot fails, and interfaces before picking how to do an action you haven't done this session.

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

Input Schema

Name	Required	Description	Default
`topic`	No	Playbook to return in full (e.g. 'recovery', 'interfaces'). Omit to list the available topics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Oct 19, 2026

addedInput schema / properties / topic / description

Added value: +"Playbook to return in full (e.g. 'recovery', 'interfaces'). Omit to list the available topics."

First observedv0.1.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the doctrine is bundled/offline, explains the re-anchoring purpose, and distinguishes listing from full-text retrieval.

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?

The purpose and invocation rules are front-loaded and easy to scan. The rationale about compacted skill files is helpful but slightly verbose for a one-parameter read-only tool.

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?

For a simple read-only lookup tool with full schema coverage and clear annotations, the description covers purpose, calling convention, and when to use key topics. No important agent decision is left unaddressed.

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 coverage is 100%, and the single optional topic parameter is already documented in the schema with examples. The description reinforces omit-vs-provide behavior but does not add syntax or constraints beyond the schema.

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 uses a specific verb and resource: "Re-serve the bundled operating doctrine" and clarifies that it returns bundled playbooks. It also distinguishes this offline, no-device-I/O tool from the sibling device-operation tools.

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

Usage Guidelines5/5

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

It explicitly states both invocation modes: no topic lists available topics, and a topic returns that playbook's full text. It further names concrete situations for recovery and interfaces, so the agent knows when to reach for it.

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