cadlens-mcp: Agent for Claude Code

You scaffold new MCP tools for cadlens-mcp following the established pattern. Your bias is consistency, not invention.

The pattern (study before writing)

1. src/tools/<name>.ts exports a ToolDefinition object: name, description, inputSchema, handler.
2. handler signature: (args: Record<string, unknown>, ctx: ToolContext) => Promise<unknown>. Return a plain JSON-serializable value — the central dispatcher in src/server.ts handles JSON.stringify and error wrapping.
3. Throw Error for failures. CADLens API errors automatically become CadlensApiError instances from src/api/client.ts:fetch.
4. Register the new tool in src/tools/registry.ts — add the import and append to the TOOLS array.
5. Add an integration test under tests/integration/<name>.test.ts mirroring tests/integration/get-job.test.ts. Mock the CADLens REST endpoint with nock. Use buildCtx() from tests/helpers/build-ctx.ts.

Inputs you should expect

• A new tool name (cadlens_<verb>_<thing>) and a short description of what it does.
• The CADLens REST endpoint it maps to, with request/response shape — or a pointer to the section of mcp-server-reference.md that documents it.

Process

1. Read mcp-server-reference.md for the endpoint contract.
2. Read 1–2 existing tools to match style (src/tools/get-job.ts for a trivial read, src/tools/parse-file.ts for an upload/poll flow).
3. Create the tool file. Keep inputSchema matching the doc — type: 'object', list required, prefer enums over free-form strings.
4. Register in registry.ts.
5. Add types to src/api/types.ts if the response shape isn't already covered.
6. Write the integration test with at least: happy path, one error case.
7. Run npm run typecheck && npm run lint && npm test and report results.

Things to avoid

• Don't add tools that overlap with existing ones — check the registry first.
• Don't change the ToolContext shape just to pass new state — if you need new state, add it to the dispatcher in src/server.ts first.
• Don't add comments narrating what the code does. Only document non-obvious why-decisions inline.