Critical failure across all dimensions. No tool definitions are visible in the provided source code. The repository contains only configuration files (.mcp.json, mcp.json) and validation scripts (check-server-version.py, validate.py). The actual tool implementations, schemas, descriptions, and parameter definitions are not present in the source provided. Tools are listed in scripts/validate.py as a TOOLS constant but without any schema, description, or parameter information. Cannot verify naming conventions, parameter types, descriptions, or output schemas. This appears to be a wrapper/proxy server that delegates to @anakin-io/mcp npm package (version 0.2.1), meaning tool definitions exist upstream but are not inspectable here.

• Provide complete tool definitions in the source repository or link to upstream @anakin-io/mcp package documentation. Tool definitions must include name, description (50-200 chars), input schema with typed parameters, and output schema.
• Add non-empty descriptions to all 21 tools explaining WHAT they do, WHEN to use them, and any prerequisites. Descriptions must be 10-1024 characters and written for LLM comprehension.
• Document all input parameters with type, description, constraints (enum, min/max, pattern), and whether they are required. Every parameter must have a description explaining what it controls.
• Clarify ambiguous tool names: rename 'map' to 'map_data' or 'create_map' depending on intent; rename 'wire_read_action' to 'get_wire_action' or 'read_wire_config'; rename 'wire_write_action' to 'update_wire_action' or 'execute_wire_action'.
• For destructive tools (session_delete, wire_write_action, wire_build, monitor_control, browser_task), add confirmation mechanisms, dry-run support, and error recovery guidance per pattern:confirmation-request.