This server exposes 30 Docker management tools via HTTP but has critical definition gaps. Tool descriptions are minimal (5-20 chars in Chinese), providing almost no context for LLM selection. Input schemas exist but lack descriptions for most parameters, LLMs cannot infer what 'query', 'cmd', 'compose_file' mean without explicit guidance. No output schemas are documented. Error handling is absent from tool definitions. The server is not an MCP server at all, it's a plain HTTP API with Gin routing, not implementing the MCP protocol. Tool definitions appear inferred from route handlers rather than explicitly registered with MCP schemas.

• Implement MCP protocol: wrap this HTTP API as a proper MCP server using an MCP SDK (e.g., mcp-go). Register tools via MCP's tool registration mechanism with full schemas and descriptions.
• Expand tool descriptions to 50-200 characters in English. Example: 'pull_image' → 'Download a Docker image from a registry (e.g., Docker Hub). Specify the image name with optional tag (e.g., ubuntu:22.04). Required before running a container.'
• Add descriptions to all parameters. Example: 'cmd' in run_container → 'Command to execute in the container (e.g., /bin/bash). If omitted, uses the image's default ENTRYPOINT.'
• Document output schemas for each tool. Example: list_images should return {images: [{id: string, name: string, size: integer, created: string}], total: integer}.
• Add confirmation/dry-run for destructive operations. Implement a 'confirm_delete_image' tool or add a 'dry_run: boolean' parameter to delete_* tools to prevent accidental data loss.