Weather API MCP Tools Design

Problem/Feature Description

WeatherWise Inc. is building an MCP server to provide weather data to AI assistants. They need a set of tools that allow agents to access current weather conditions, forecasts, historical data, and weather alerts. The tools should be intuitive for AI agents to discover and use, with clear naming that indicates their purpose.

The company has a REST API with these endpoints:

• GET /current?location={city}&units={metric|imperial} - current weather
• GET /forecast?location={city}&days={1-7}&units={metric|imperial} - multi-day forecast
• GET /history?location={city}&date={YYYY-MM-DD}&units={metric|imperial} - historical weather
• GET /alerts?location={city}&severity={low|medium|high} - weather alerts
• POST /subscribe?location={city}&email={email} - subscribe to alerts

They want to expose these as MCP tools that agents can call directly. The tools should work well together and be easy for agents to understand based on their names alone.

Output Specification

Design the MCP tool definitions for this weather API. Create a JSON file weather_tools.json containing an array of tool definitions. Each tool definition should include:

1. name - The tool name
2. description - Brief description of what the tool does
3. parameters - Array of parameter definitions (name, type, description, required, etc.)
4. returns - What the tool returns

Focus on creating intuitive, well-organized tool names that follow consistent patterns. The tools should be discoverable and predictable for AI agents.

Create at least 5 tools covering the main API endpoints. Ensure the tool names make sense together as a family of related weather tools.

Notes

• The tools will be used by AI agents across different platforms (Claude, ChatGPT, etc.)
• Agents should be able to guess what a tool does from its name
• Related tools should be easy to find together
• Avoid implementation details in tool names or descriptions