This server exposes only a single tool ('test') with a trivial definition. The tool has no input schema (empty object {}), a generic 2-word description ('Test endpoint for Ableton Live connection'), and no parameter documentation. The codebase is not an MCP server at all, it is a plain Express HTTP API that does not implement the MCP protocol. No tool registration, no MCP message handling, no protocol compliance. This is a fundamental misclassification.

• Implement the MCP protocol: add MCP message routing (initialize, call_tool, etc.), tool registration with proper schemas, and stateless request handling per spec 2026-07-28.
• Add a proper input schema to 'test' with typed parameters and descriptions. Even a read-only test should declare what it accepts (e.g., timeout_ms: integer, optional).
• Expand tool description to 50 - 150 characters explaining: what the tool does (tests Ableton Live connection), when to call it (before other operations), and what it returns (connection status, version info).
• Document the output schema: define the structure of the OSC response (e.g., { status: string, version?: string, error?: string }).
• Add error handling that returns structured errors with recovery hints: 'Connection failed. Ensure Ableton Live is running on 127.0.0.1:11000 and listening on 11001.'