NextChat-MCP exhibits severe definition quality gaps. Tool schemas are inferred from code rather than explicitly visible in registration. Descriptions exist but lack LLM-optimization guidance (e.g., 'Retrieves all MCP servers' is generic; no mention of when to call or what to expect). Parameters lack type definitions in visible schema declarations. No error handling guidance, no output schema documentation, and no parameter constraints (enums, ranges). The server appears to be a Next.js application wrapping MCP concepts rather than a proper MCP server implementation. Tool definitions are scattered across utility files without centralized, schema-compliant registration.

• Add formal JSON Schema definitions for all tool inputs. Each parameter must declare 'type' (string, number, boolean, object, array), 'required' status, and constraints (enum, minLength, maxLength, pattern, minimum, maximum). Example: {"serverId": {"type": "string", "description": "UUID of the MCP server", "minLength": 36, "maxLength": 36}}
• Expand tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to call it, and WHAT it returns. Example: 'Retrieves all MCP servers created in this workspace. Call this first to list available servers before deploying or deleting. Returns array of {id, name, description, status, url}.'
• Document output schemas for all tools. Define the structure of returned objects, field types, and required fields. Example: get_mcp_servers returns {servers: [{id: string, name: string, description: string, status: 'active'|'inactive', url: string}], total: number}
• Add error handling guidance to descriptions. For delete_mcp_server: 'If server not found, returns 404 with message "Server ID not found. Call get_mcp_servers() to list available servers." Deletion is irreversible.'
• Implement confirmation pattern for destructive operations. Add a 'confirm' boolean parameter to delete_mcp_server, or create a separate delete_mcp_server_confirm tool that requires explicit user approval before deletion.