validate_engineering_units — BlockWerk MCP Tool
validate_engineering_units
(validate engineering units) is one of 42 tools on the
BlockWerk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_engineering_units from your client
- Claude Code BlockWerk validate_engineering_units run in your project directory
- Claude Desktop BlockWerk validate_engineering_units ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BlockWerk validate_engineering_units ~/.cursor/mcp.json
- VS Code BlockWerk validate_engineering_units .vscode/mcp.json
- Zed BlockWerk validate_engineering_units ~/.config/zed/settings.json
- Windsurf BlockWerk validate_engineering_units ~/.codeium/windsurf/mcp_config.json
- Cline BlockWerk validate_engineering_units ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BlockWerk validate_engineering_units ~/.gemini/settings.json
- Grok BlockWerk validate_engineering_units .mcp.json (in your project root)
- ChatGPT BlockWerk validate_engineering_units Settings → Connectors → Advanced → Developer mode
- Claude.ai BlockWerk validate_engineering_units Settings → Connectors → Add custom connector
- LangChain BlockWerk validate_engineering_units pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://blockwerk-mcp-worker.blockwerk.workers.dev/Other tools on this server
- describe_canvas
- get_available_blocks
- add_block
- connect_blocks
- update_params
- delete_block
- load_diagram
- export_diagram
- get_share_link
- clear_canvas
- tidy_layout
- batch_commands
- analyze_topology
- get_signal_data
- calculate_metrics
- get_analysis_measurements
- evaluate_spec_mask
- get_architect_memory
- update_architect_memory
- validate_canvas
- get_canvas_preview
- get_templates
- load_template
- run_simulation
- sweep_parameter
- optimize_parameters
- optimize_multi_parameter
- auto_tune_pid
- identify_fopdt
- start_optimization
- get_job_status
- cancel_job
- list_jobs
- explain_simulation
- get_bode_data
- get_fft_data
- get_engine_status
- generate_code
- undo_last_ai_action
- redo_last_ai_action
- get_ai_history
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.