MCPfinder has 5 tools with clear verb-noun naming (search_, get_, add_, remove_, list_). All tools have descriptions (avg ~100 chars, within baseline). Input schemas are present and use Zod validation with type definitions. However, parameter descriptions are sparse or missing in several tools, output schemas are not documented, and error handling lacks recovery guidance. The server mixes read-only and write operations without clear permission boundaries. No tool annotations (readOnlyHint/destructiveHint) despite having both read and destructive operations.

• Document output schemas for all tools. E.g., search_mcp_servers returns array of {id, name, description, url, tags}; get_mcp_server_details returns {id, name, description, url, tags, command, env, workingDirectory}. Include these in tool descriptions or as separate schema documentation.
• Add tool annotations: mark search_mcp_servers, get_mcp_server_details, list_mcp_server_configs with readOnlyHint=true; mark add_mcp_server_config and remove_mcp_server_config with destructiveHint=true and idempotentHint=false (or true if idempotent).
• Enhance error messages with recovery guidance. E.g., 'Failed to fetch from MCP Finder API (status 404). The server may be offline. Retry in 30 seconds or check https://mcpfinder.dev/status.'
• Add pagination parameters to search_mcp_servers and list_mcp_server_configs: limit (1-100, default 20), offset (default 0). Return total_count and next_offset in response.
• Clarify ClientIdentifierSchema in parameter descriptions: 'Provide EITHER client_type (e.g., "cursor", "claude") OR config_file_path (absolute or ~-prefixed), but not both. If neither provided, defaults to ~/.cursor/mcp.json or equivalent.'