# prepare_design_doc

Call this when the user runs /design-doc. Gathers local git context and the section template, and returns drafting instructions. You (Claude) then draft the actual document from this template plus your own knowledge of what was just done in this session, and finally call save_design_doc with the result.

Agent View of the PolicyLayer registry record for `prepare_design_doc`. HTML page: https://policylayer.com/tools/design-doc-generator-mcp/prepare-design-doc

## Facts

- Tool: `prepare_design_doc`
- Server: Design Doc Generator (`design-doc-generator-mcp`) — https://policylayer.com/tools/design-doc-generator-mcp.md
- Install: `npx -y design-doc-generator-mcp`
- Homepage: https://www.npmjs.com/package/design-doc-generator-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `mode` | string | no | Document mode: 'default' for a standard design doc, 'root-cause' for a bug investigation, or 'comparison' for an approach comparison. Infer from the nature of t |
| `projectRoot` | string | no | Absolute path to the project root. Defaults to the server's current working directory. |
| `sessionSummary` | string | yes | Your own summary, in your words, of the technical work done in this session so far: the problem, what was tried, what changed, and any alternatives or open issu |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "prepare_design_doc",
    "arguments": {
      "sessionSummary": "<sessionSummary>"
    }
  }
}
```

## Why prepare_design_doc is rated Low

The tool reads local git context and retrieves a section template, then returns instructions. It does not write, execute, delete, or move money. The actual document creation is done by a subsequent call to save_design_doc. Gathering git context is a read operation with minimal blast radius.

From the tool's own definition: "Gathers local git context and the section template, and returns drafting instructions"

## Use case

AI agents call prepare_design_doc to retrieve information from Design Doc Generator without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Design Doc Generator:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_design_doc": {}
  }
}
```

## Other tools on Design Doc Generator (2)

- `activate_license` — Write — https://policylayer.com/tools/design-doc-generator-mcp/activate-license.md
- `save_design_doc` — Write — https://policylayer.com/tools/design-doc-generator-mcp/save-design-doc.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=design-doc-generator-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/design-doc-generator-mcp