This is a desktop Electron application (NeoXider Agent Deck), not an MCP server. The three tools (glob, grep, read) are defined in smoke test scripts (multi-tool-parity-smoke.cjs, tool-call-smoke.cjs), not in a proper MCP server implementation. Tool definitions are inferred from test harness calls, not explicitly registered via MCP protocol. No MCP server code, transport layer, or protocol implementation is visible. The tools themselves are read-only file operations with minimal descriptions and incomplete schemas. This appears to be a desktop UI for DeepSeek Harness sessions, not an MCP-compliant tool server.

• Implement a proper MCP server using the official MCP SDK (Python, TypeScript, or Go). This application should expose tools via the MCP protocol, not embed them in test scripts.
• Create explicit tool definitions with full JSON Schema input/output specifications. Document expected return types (e.g., glob returns array of file paths; grep returns array of matching lines with line numbers).
• Expand tool descriptions to 100-200 characters. Include WHEN to use each tool, WHAT it returns, and any prerequisites. E.g., 'Search for lines matching a regex pattern in a file. Returns matching lines with line numbers. Use after glob() to find files, then grep() to locate content within them.'
• Add parameter constraints: glob pattern (string, required), grep pattern (string, required, regex format), file path (string, required, must exist), lines (number, optional, min=1, max=10000).
• Document error cases and recovery guidance. E.g., 'If no matches found, return empty array. If file not found, return error with available files in directory.'