Critical failures across all dimensions. The single tool 'execute_skill_action' has no visible input schema, no parameter descriptions, and a generic description (47 chars) that fails to explain what the tool actually does or when to use it. The mcp_server.py file contains only a stub that prints JSON and exits, it does not implement the MCP protocol at all. No tool registration, no schema validation, no error handling. This is a non-functional skeleton, not a production MCP server.

• Implement the MCP protocol message loop in mcp_server.py. Handle initialize, list_tools, call_tool, and complete_request messages per the MCP 2026-07-28 spec.
• Define a complete JSON Schema for execute_skill_action input parameters. Include robot_hardware_chassis (enum: QUADRUPED_WITH_MOUNTED_ARM, BIPEDAL_HUMANOID_ROBOT, etc.), terrain_environment (enum: STAIRS_AND_UNSTRUCTURED_RUBBLE, SLIPPERY_INDUSTRIAL_FACTORY_FLOOR, etc.), and any other required inputs with type and description.
• Expand tool description to 100-200 characters. Example: 'Plan cross-embodiment robotic locomotion and manipulation for a given robot chassis and terrain. Returns planner ID, stability margin, and zero-shot transfer verification. Required params: robot_hardware_chassis, terrain_environment.'
• Document the output schema. Specify that the response includes brain_planner_id (string), embodiment_type (string), environment (string), terrain_adaptation_frequency_hz (number), dynamic_balance_stability_margin_pct (number), cross_hardware_zero_shot_transfer_verified (boolean), and locomotion_energy_efficiency_score (number).
• Add error handling. Return structured errors with actionable guidance, e.g., 'Invalid robot_hardware_chassis: got "UNKNOWN_ROBOT", must be one of: QUADRUPED_WITH_MOUNTED_ARM, BIPEDAL_HUMANOID_ROBOT, etc.'