This server has only ONE tool (health_check) with an empty input schema {}. The tool has a basic description but no input parameters to evaluate. The server itself is a container wrapper offering multiple manager-based tools (Bash, Python, File, Web, Knowledge Base, List, Market, RSS), but these are NOT registered as MCP tools in the visible code. The main.py file shows manager imports but no tool registration via @mcp.tool() decorators or explicit tool.define() calls. The 'cmcp.tools.register_all_tools()' function is imported but not shown in source, making it impossible to verify actual tool definitions. Only health_check is visible and directly registered. This server appears to be a foundational framework that SHOULD expose container management tools but does not demonstrate their actual MCP registration in the provided code.

• Add explicit JSON Schema to health_check input (currently empty {}). Even if no parameters are needed, declare 'type: object' with 'properties: {}' and 'required: []'.
• Expand health_check description to 100-150 chars. Example: 'Check if Container-MCP server is running and healthy. Returns status, service name, and transport type. Use before attempting other operations.'
• Document health_check output schema in the tool definition. Declare that it returns {status: string, service: string, transport: string} with example values.
• Implement toolAnnotations for health_check via FastMCP decorator: @mcp.tool(name='health_check', description='...', readOnlyHint=true) to signal it has no side effects.
• Expose the implementation of register_all_tools() in source code so all Bash, Python, File, Web, Knowledge Base, List, Market, and RSS tools can be audited against this rubric. Currently they are hidden.
• For each manager-based tool, add descriptions explaining: WHAT it does, WHEN to use it vs similar tools, WHAT parameters are required, WHAT the output structure is, and HOW to handle errors.
• Add parameter descriptions to all manager tools. Do not assume LLMs will infer what 'cmd', 'code', 'path', or 'query' mean, explicitly state format, constraints, and examples.
• Implement error handling with recovery guidance. E.g. if a bash command fails: 'Command failed (exit code 1). Check syntax and try again, or use list_files to verify paths.' Do not return raw stderr.
• For destructive tools (delete_file, kill_process), add a dry-run or confirmation step to prevent accidental data loss.

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

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