This server has severe definition quality issues. Tool definitions are inferred from Python FastMCP decorators rather than explicitly visible in the Rust codebase. The source shows a Rust FUSE filesystem server (LiveFolders) with a custom Tool trait, but the actual MCP tool implementations are scattered across research/criteria Python files with minimal descriptions. 12 of 13 tools have descriptions under 100 chars (baseline 194). No input schemas are visible in the Rust code, only Python type hints. Duplicate tool names (list_users appears 3 times). No error handling guidance, no output schemas documented, no parameter constraints. The server appears to be a research artifact mixing multiple test implementations rather than a cohesive production MCP server.

• Consolidate duplicate 'list_users' into a single canonical tool with clear output format (JSON array with id, name, createdAt, avatar fields).
• Add output schemas to all tools. Document return type as JSON object with typed fields, not free-form strings. E.g., search_user should return {results: [{id: string, name: string}], total: number}.
• Expand descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use search_user for partial name lookup; use get_user when you have the exact ID'). Add dependency hints.
• Add error handling guidance. E.g., get_user: 'Returns error if user_id not found. Try search_user() with a partial name first.'
• Document parameter constraints in descriptions. E.g., search_user name param: 'Case-insensitive substring (1-100 chars). Returns up to 50 matches.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry