🌤️ feat: Add OpenWeather Tool for Weather Data Retrieval

[danny-avila]

Originally #5206

Summary

Added OpenWeather integration as a structured tool for LibreChat. This integration provides:

• Current weather and forecasts
• Historical weather data
• Daily weather summaries
• Human-readable weather overviews
• Temperature unit conversion (Celsius, Fahrenheit, Kelvin)
• Multi-language support for weather descriptions
• Geocoding support (city names to coordinates)

The tool uses OpenWeather's One Call API 3.0, which offers a free tier with 1,500 API calls per month.

This PR demonstrates rapid plugin development using AI assistance - the entire implementation, including comprehensive tests and documentation, was completed in about 3 hours while multitasking.

Features

• Current weather and forecasts
• Historical weather data (back to 1979)
• Daily weather aggregations
• Natural language weather summaries
• Support for multiple temperature units
• Multi-language support
• City name or coordinate-based queries
• Comprehensive error handling
• Full test coverage

Change Type

Please delete any irrelevant options.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Testing

npm test -- app/clients/tools/__tests__/openWeather.test.js

export OPENWEATHER_API_KEY=YourAPIKeyHere
npm test -- app/clients/tools/__tests__/openWeather.integration.test.js

In addition, it is easy enough to test from with LC. I can provide an API key for testing privately.

Documentation

PR submitted at LibreChat-AI/librechat.ai#196

[danny-avila]

@jmaddington One thing I noticed is that this isn't setup for user-provided keys.

Part of the logic involves getEnvironmentVariable, which is why the test is failing:

   ● OpenWeather Tool (Integration Test) › timestamp action with real API key returns historical data

    Missing OPENWEATHER_API_KEY environment variable.

      11 |   const key = getEnvironmentVariable(envVar);
      12 |   if (!key && !override) {
    > 13 |     throw new Error(`Missing ${envVar} environment variable.`);
         |           ^
      14 |   }
      15 |   return key;
      16 | }

I'll add it when I get the chance

[jmaddington]

@danny-avila I'd be glad to provide a key, or we can skip the integration tests if the key doesn't exist. While mock tests are great, I personally have a high preference for live integration tests when it is feasible.

[danny-avila]

All good, I meant that the current code was not allowing users to provide their own keys from the UI.

Coded tools need to follow a simple authentication pattern to allow for this, see my changes here:
8731f43

[danny-avila]

I can add my own key once it's activated for live testing