This is a tutorial/demo repository, not a production MCP server. Tool definitions are scattered across multiple tutorial files with inconsistent quality. Most tools lack proper descriptions (under 20 chars or missing entirely). Schemas are present but minimal. Two tools share the identical name 'get_weather' (tools 6 & 7), creating ambiguity. The write_file tool (tool 8) is a security risk with no input validation. No error handling guidance. Tool composition is poor, tools are isolated examples rather than a coherent service.

• Rename one 'get_weather' tool to 'get_weather_openweather' or 'get_weather_chinese' to eliminate ambiguity. Ensure tool names are globally unique within the server.
• Expand tool descriptions to 50 - 200 characters. Include WHEN to use each tool and what it returns. E.g., 'Get current weather for a location using OpenWeather API. Returns temperature, conditions, and wind speed. Use this before suggesting outdoor activities.'
• Add input validation and sanitization to write_file: restrict file paths to a safe directory, validate content length, and reject suspicious patterns. Return clear error messages on validation failure.
• Add error handling to all tools. Return structured errors with recovery hints: 'ROS2 node not initialized. Ensure turtlesim is running: ros2 run turtlesim turtlesim_node'
• Consolidate all tools into a single FastMCP server definition with clear composition. Document which tools chain together (e.g., ros2_topic_list → move_robot).

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

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