This is a Next.js web application, not an MCP server. The codebase contains HTTP API endpoints (Next.js pages/api routes) and React UI components, but lacks MCP protocol implementation. Tools are inferred from API route files rather than explicitly registered via MCP. No tool schemas are visible in source code, parameter definitions exist only in the evaluation input, not in actual code. Descriptions are present but generic. No error handling guidance, no output schemas documented, no pagination support visible. The server cannot function as an MCP server without MCP protocol transport and tool registration.

• Implement MCP protocol: wrap this Next.js app as an MCP server using the official MCP SDK (Node.js). Register tools via server.tool() with explicit schemas, not HTTP routes.
• Add explicit input schemas to every tool in code. Use JSON Schema with type, description, enum, and required fields. Verify schemas match parameter definitions in evaluation.
• Expand tool descriptions to 50 - 200 characters. Include WHAT the tool does, WHEN to use it, and any prerequisites. E.g., 'generateDockerfile: Creates a production-ready Dockerfile for the generated TypeScript MCP server. Call after generateTypeScriptServer() to containerize the output.'
• Document output schemas for every tool. Specify response structure, field types, and pagination (if applicable). E.g., 'POST /api/contracts returns {contractId: string, address: string, network: string, abiJson: object, createdAt: ISO8601}'.
• Rename tools to follow verb_noun convention: 'create_contract', 'get_contract_schema', 'generate_typescript_server', 'list_projects'. This makes tool intent clear to LLMs without reading descriptions.