This is a Rust/Tauri desktop application, NOT a functional MCP server. The codebase contains React/TypeScript UI components and a Tauri backend, but NO actual MCP server implementation is evident from the provided source. The tool definitions listed appear to be aspirational or UI mockups rather than registered, working MCP tools. The project has MCP client dependencies (rmcp crate with client features) but no server registration, message handlers, or protocol-compliant tool definitions. The 4 tools listed lack visible implementations, proper schemas, and error handling. This is a fundamental architectural gap, the project attempts to USE MCP servers (as a client), not expose tools via MCP.

• Implement a proper MCP server handler (initialize, tools, call_tool messages) using the rmcp server transport. Currently, the project only has client dependencies.
• Move api_key out of tool parameters. Inject provider credentials server-side via environment variables or a secure vault. Never expose secrets as tool inputs.
• Expand tool descriptions to 50-200 characters with explicit WHEN guidance. Example: 'Read and list files in a directory. Returns entries with name, path, is_directory, size, and extension. Useful for exploring file structures before processing. Supports paths up to 1000 characters; returns max 100 entries per call.'
• Add output schema documentation for each tool. Define return object structure with typed fields. For send_message_stream, specify the structure of chat_stream event chunks.
• Implement per-tool error handling with recovery guidance. E.g., 'Path not found. Verify the path exists and you have read permissions. Try get_default_directories() to discover valid base paths.'
• Convert free-form 'provider' parameter to an enum. Valid values: ['openai', 'anthropic', 'gemini', 'local']. Add description: 'AI provider name, determines API endpoint and model availability.'
• Add pagination to read_directory. Support limit (1-100, default 20) and offset parameters. Return total_count. Prevent context window exhaustion from large directory listings.
• Document all parameter constraints in descriptions. E.g., 'path: Absolute or relative directory path (max 1000 chars). Supports Unix and Windows paths.' Do NOT put example values in descriptions, use enum constraints instead.