This server exhibits severe definition quality issues across all dimensions. Tool descriptions are generic or misleading (e.g., 'List all containers or only running ones' repeated verbatim for 3 unrelated tools). Parameter descriptions are sparse or absent. Schemas lack proper type definitions for many parameters. No error handling guidance. Security-critical tools (execute_remote_command, remote_* SSH tools) expose credentials as parameters, violating secret-injection patterns. Tool naming is inconsistent (dataset_* vs remote_* vs execute_*). No output schemas documented. The server bundles 10 disparate tools (web fetch, document reader, MongoDB dataset queries, SSH remote execution, markdown conversion) with no coherent composition or chaining support.

• Move SSH credentials (username, password) to server-side environment variables or a vault. Accept only hostname and port as parameters. Document in tool description: 'SSH credentials are configured server-side for security.'
• Rewrite tool descriptions to be distinct and LLM-optimized (50-200 chars). Example: 'execute_remote_command' → 'Execute a shell command on a remote server via SSH. Returns stdout, stderr, and exit code.' 'remote_list_containers' → 'List Docker containers on a remote server. Optionally filter to running containers only.'
• Document output schemas for all tools. Example for dataset_find: 'Returns {documents: [{id, title, content, url}], total: int, limit: int}'. This enables LLMs to chain tools and extract required fields.
• Add parameter constraints and formats to descriptions. Example: 'limit' → 'Maximum number of results to return (1-100, default 10)'. 'url' → 'Full HTTP(S) URL starting with http:// or https://'.
• Implement error handling with recovery guidance. Example: 'If SSH connection fails, verify hostname, port, and network connectivity. If authentication fails, check server-side credentials configuration.'