Skip to content

docs: a generated MCP tool reference; fix contradictory living docs - #82

Merged
Madraka merged 1 commit into
mainfrom
docs/mcp-tool-reference
Oct 22, 2026
Merged

Madraka merged 1 commit into
mainfrom
docs/mcp-tool-reference

Conversation

@Madraka

@Madraka Madraka commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Generated MCP tool reference

scripts/mcp-tools-doc.ts writes packages/mcp-server/README.md#tool-reference from defineTools(): all 102 tools in server order, with scopes, kind (read / write / destructive), approval (always a person / depends on the call / by mode) and the first sentence of the description. Angle brackets are escaped outside code spans, and a cut never leaves a code span open. node scripts/mcp-tools-doc.ts --check is in pnpm check and CI.

The README's old "deterministic order" list named only about 45 of the tools.

Living docs fixed (from an audit of about 33 items)

Principle: a number or list that drifts points to its source instead of copying it. RFCs, CHANGELOGs and reports are left alone.

Where What was wrong
README.md "20 semantic MCP tools" (×2) → over 100 with a link; CLI list → --help / the CLI reference; Studio "en/tr" → 19 languages; skills and guides → links
README.md, CONTRIBUTING.md, AGENTS.md three different descriptions of pnpm check → one
AGENTS.md command list → help.ts; the translate skill added; lazy namespaces → namespaces.ts; jsonschema 0.59
docs/agents/README.md patch_draft is for pages, not article bodies; tool count → the reference
packages/agent-runtime/README.md the stale scope list → KEY_SCOPES/PERSON_SCOPES, roles
packages/cli/README.md the incomplete usage block → --help, the reference, common commands
docs/guides/comments.md, schedules.md "Studio screens still being built" (they exist); time-zone field; History › Approvals
translations-weblate.md, analytics-privacy.md language count and cost estimate; string locations
.agents/skills/add-capability described a capabilities/ runtime that never shipped → today's process
studio-ui skill, DESIGN.md conflicting Kumo counts → pnpm kumo ls
starters/blog/README.md said the entryPath fallback was kept in 0.3.11 (it was restored in 0.3.13)
code-structure.md, server-instructions.ts, packages/api/README.md the render-check path; the approval sentence now defers to the mode; /pending route and Bearer auth
ADR-0003, ADR-0004, ADR-0006 dated addenda for decisions the code did not follow
DESIGN.md Collections settings; live-site links and pending changes

Checks

  • mcp-tools-doc --check and the size ratchet pass.
  • docs site tests (including the link checker) 33/33; mcp-server 145/145; api mcp.test.ts 9/9.

🤖 Generated with Claude Code

- scripts/mcp-tools-doc.ts writes the MCP server README's tool reference
  (all 102 tools: scopes, kind, approval, first sentence) from
  `defineTools()`; `pnpm check` and CI fail when it is stale. The README's
  hand-written "deterministic order" list named about 45 of them.
- Counts and lists that drift now point to their source: "20 semantic MCP
  tools" (README, twice) → over 100 with a link to the reference; CLI
  command lists → `cloudhal --help` / the CLI reference; scopes →
  `KEY_SCOPES`/`PERSON_SCOPES`; lazy namespaces → `namespaces.ts`.
- Stale statements: comments and schedules guides said their Studio
  screens were still being built; Studio has 19 languages, not en/tr;
  `patch_draft` patches pages, not article bodies; the add-capability
  skill described a `capabilities/` runtime that never shipped; the
  starter README misdated the `entryPath` fallback; jsonschema 0.59; the
  `RENDER_CHECK_SCRIPT` path; the server instructions' unconditional
  approval sentence.
- ADR-0003, ADR-0004, ADR-0006: dated addenda for decisions the code did
  not follow.
- DESIGN.md: Collections settings, live-site links and pending changes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Madraka <[email protected]>
@Madraka
Madraka merged commit 806681b into main Oct 22, 2026
6 of 7 checks passed
@Madraka
Madraka deleted the docs/mcp-tool-reference branch October 22, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant