The server exposes only ONE tool ('traps'), which is a read-only resource delivery mechanism, not an actionable tool. The tool itself lacks a proper input schema, parameter descriptions, and structured output documentation. The server's actual CAD functionality (128 tools mentioned in pyproject.toml) is NOT exposed through the MCP interface, it is implemented in AutoLISP bridge code (bridge/mcp_bridge.lsp) but not registered as MCP tools in server.py. Only 'traps' is registered via @mcp.resource(), which returns unstructured markdown text rather than a composable tool response. This is a critical architectural gap: the server advertises 128 CAD tools but exposes zero of them to MCP clients. The single exposed 'tool' is effectively a static documentation fetch, not a real tool.

• Register all 128 CAD tools as proper MCP tools with @mcp.tool() decorators. Each tool (e.g., draw_circle, measure_distance, boolean_union, export_stl) must have an explicit name, description (50-200 chars), and JSON Schema input parameters.
• Define input schemas for each CAD tool. Example: draw_circle(center_x: float, center_y: float, radius: float, layer: str='0', color: int=256) with descriptions like 'center_x: X coordinate in millimeters (reference frame origin at [0, 0]).'
• Reformat 'traps' output as structured JSON instead of markdown. Return an array of objects: [{trap_id, trap_name, category, description, severity, mitigation_steps}]. This allows LLMs to index and reference specific traps programmatically.
• Improve 'traps' description to explain when to use it: 'Retrieve hard-won failure modes and safety rules for CAD modeling with this server. Call before starting a long modeling session to avoid costly geometry errors, boolean failures, and bridge synchronization issues. Returns structured guidance on geometry pitfalls, boolean-operation gotchas, LISP heap limits, and entity handle lifecycle.'
• Document the relationship between tools and the INSTRUCTIONS constant (LISP bridge rules, multiline expression handling, etc.). Current INSTRUCTIONS are free-form text; formalize them as schema constraints on tool parameters (e.g., 'expressions must be complete single-line S-expressions').
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to each CAD tool. Mark measurement tools as readOnlyHint=true, boolean operations as destructiveHint=true, and geometry writes as idempotentHint=false (since repeated calls may fail if entity state changes).