Critical failure: Tool definitions are inferred from UI component filenames and descriptions only. No actual tool registration code, input schemas, or output schemas are visible in the provided source. The 13 tools listed (bash, edit, read, write, glob, grep, list, patch, todowrite, todoread, webfetch, websearch, question) appear in React component files (ToolsSection.tsx, CustomToolsSection.tsx) but no MCP SDK registration, Zod schemas, or handler implementations are shown. Without seeing the actual tool definitions in code, all per-tool scores are capped at 50 per the rubric. Descriptions are trivial (1-5 words: 'Execute bash commands', 'Edit file contents'). No parameter documentation visible. No output schemas documented. This is a UI configuration layer, not an MCP server implementation.

• Locate and provide the actual MCP server implementation file (likely in resources/mcp-servers/ or src/). The current source shows only UI configuration, not tool registration.
• For each tool, write a 50-200 character description explaining WHAT it does, WHEN to use it, and what it returns. Example: 'Execute a bash command and return stdout/stderr. Use for file operations, system checks, or running scripts. Returns {stdout, stderr, exitCode}.'
• Define input schemas using Zod or JSON Schema with explicit types and descriptions for every parameter. Example: bash needs {command: string, cwd?: string, timeout?: number}.
• Document output schemas. Example: read returns {content: string, encoding: string, size: number}; list returns {items: [{name, type, size}], total: number}.
• Add error handling guidance to destructive tools (bash, edit, write, patch). Include recovery instructions: 'If write fails with EACCES, check file permissions. Use chmod_file to fix.'