Bug: `find_files` returns a string on error, causing validation failure

[g1331]

Calling the tool without setting the project path has a probability of triggering this issue.

[johnhuang316]

Hi @g1331,

MCP entry points now raise a dedicated MCPToolError, so FastMCP surfaces structured errors instead of raw strings. ind_files no longer returns a bare string on failure, so validation no longer blows up when the project path isn’t set. This will be part of the next release—once you’re on the latest version it should be resolved.