Weather MCP server has two clearly defined tools with proper schemas and descriptions, but falls short of production quality in several key areas. Both tools use explicit Zod schemas with proper type constraints (latitude/longitude ranges, state code length). Descriptions are present and reasonably specific ('Get weather alerts for a state', 'Get weather forecast for a location'). However, error handling is minimal (generic 'Failed to retrieve' messages with no actionable recovery guidance), output schemas are undocumented (no specification of what fields the formatted text will contain), and there is no pagination support despite potentially returning large alert lists. The implementation is functional but lacks sophistication in error classification and response structuring that would allow agents to reason about failures and adapt.

• Add error classification to all error paths: distinguish retryable (network/timeout), user-fixable (invalid input), and fatal (service down) errors. Return a structured error object with 'type', 'message', and 'suggestion' fields.
• Enhance error messages with actionable recovery guidance. Example: 'Failed to retrieve forecast data (HTTP 404). This may indicate the coordinates are outside the US. NWS API only supports US locations and territories.'
• Document the output schema for both tools. Instead of returning free-form formatted text, return a structured object: for get_alerts, {alerts: [{event, area, severity, status, headline}]}, for get_forecast, {location: {lat, lon}, periods: [{name, temperature, unit, wind_speed, wind_direction, forecast}]}.
• Add limit and offset parameters to get_alerts. Example: add optional 'limit' (1 - 100, default 20) and 'offset' (default 0) to control result size and enable pagination.
• Update get_forecast description to explicitly state: 'Get weather forecast for a US location (only National Weather Service coverage areas supported). Provide latitude and longitude in decimal degrees.'
• Replace example values in descriptions with format constraints. Change 'Two-letter state code (e.g. CA, NY)' to 'Two-letter US state code (e.g., CA, NY, TX). Must be uppercase.'
• Validate input early and return clear error messages. For example, if a state code is not exactly 2 characters, return 'Invalid state code: must be exactly 2 uppercase letters (e.g., CA, NY). Got: "xyz".'