This server exposes only 1 tool (getWeather) with minimal definition quality. The tool has a basic description and input schema, but lacks depth, error handling guidance, and output documentation. The schema is present but minimalistic. The description is generic and does not explain when to use the tool, what it returns, or error recovery paths. No parameter validation constraints, no output schema documentation, and no error categorization. The tool name is acceptable (verb_noun form), but the overall definition falls well short of production standards.

• Expand tool description to 100-200 characters. Include: what data is returned (temperature, conditions, forecast), when to call it, and what happens if location is not found. Example: 'Fetch current weather and 5-day forecast for a location (city name, ZIP, or coordinates). Returns temperature (°C), conditions, humidity, wind speed. Returns error if location not found, try a broader location name.'
• Add validation constraints to the 'location' parameter. Document accepted formats: 'City name (e.g., London, New York), ZIP/postal code, or coordinates (lat,lon). Partial matches supported.'
• Document the output schema explicitly. Example: '{ temperature: number (°C), condition: string (e.g., sunny, cloudy, rainy), humidity: number (0-100), wind_speed: number (km/h), forecast: [{ date: string (ISO 8601), temp_high: number, temp_low: number, condition: string }] }'
• Add error handling guidance to the description. Example: 'If location is not found, try: (1) a broader region name, (2) the nearest major city. If the API is unavailable, retry after 60 seconds.'
• Verify and expose the complete tool definition from extensions/example.ts in source code review. Ensure schema, input validation, and error paths are visible and production-ready.

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

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