docs-style-tonelisted

# docs-style-tone — Style and Tone Analysis ## Workflow 1. **Connect to Docsbook** — run `list_workspaces` to find the workspace, then `get_doc_graph` to get all pages. Offer to add the repo if not indexed. Reindex with `reindex_doc_graph` if graph is empty or stale. 2. **Read page content** — use `read_doc_sections` to access text for each page. Sample a few pages across different types (tutorial, reference, how-to) to calibrate general style before flagging specifics. 3. **Apply checklist** — check voice and person, filler and marketing words, sentence length and structure, headings, and terminology consistency. Apply tone expectations per page type. 4. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Do not edit any documentation files — surface findings only. - Ask whether the project has a style guide before starting — analyze against that if yes, use defaults if no. - Flag passive voice in instructions; passive in reference pages may be intentional — ask the user about the strictness level. - "Simply", "just", "easily" — flag for review, not removal — context determines whether they're condescending. - Terminology inconsistency is only a problem when the same concept has multiple names — precise technical synonyms used in appropriate contexts are not flagged. ## MCP Tools | Tool | Purpose | |------|---------| | `mcp__docsbook__list_workspaces` | Find workspace | | `mcp__docsbook__get_doc_graph` | Page list | | `mcp