Helix is a Next.js application, not an MCP server. No MCP protocol implementation detected. Tools are registered in a custom tool-registry.ts with minimal schema documentation. Only 2 of 36 tools have visible input schemas (india_iip_index, web_search, todo_write). Most tools lack parameter descriptions, type definitions, and output schemas. Descriptions are present but generic (10-50 chars). No error handling guidance, no permission gates, no audit trails. This is a monolithic agent framework, not a production-grade MCP server.

• Migrate to MCP protocol: implement a proper MCP server (HTTP+SSE or Streamable HTTP) that exposes tools via the MCP Tools interface. This is not a refactor, it's a fundamental architectural change.
• Add complete input schemas to all 34 tools lacking them. Use JSON Schema with type, description, enum, minLength, maxLength, pattern, and default for every parameter. Reference the india_iip_index tool as a model.
• Expand tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it (vs. similar tools), and any prerequisites. Example: 'Search the agent's knowledge base for documents matching a query. Use this before run_code to gather context. Returns ranked results with relevance scores.'
• Add error handling guidance to all WRITE and DESTRUCTIVE tools. Include recovery hints (e.g., 'If spawn_subagent fails with timeout, retry with a simpler task'), retry classification (retryable vs. user-fixable), and confirmation steps for irreversible operations.
• Implement permission gates and audit logging. Gate destructive tools (learning_memory_delete, modify_own_prompt) behind scope checks. Log all tool invocations with user ID, timestamp, parameters, and result for compliance and debugging.