Loading ToolBench
Current weather and 7-day forecast -- temperature, humidity, wind, precipitation. Any location worldwide.
Single tool 'data_get_weather' has a strong description (340+ chars) with clear use cases and anti-patterns documented. However, the input schema is severely underspecified: three parameters (latitude, longitude, city) lack type constraints, descriptions are minimal (e.g., 'Latitude (-90 to 90)' is a range, not a description), and the required array is empty despite latitude/longitude being mutually exclusive with city. No output schema is documented. The tool name follows verb_noun convention but the schema quality is below production baseline.
Use this when you need current weather conditions or a 7-day forecast for any location. Returns weather data in JSON. Returns: 1. current (temperature, humidity, windSpeed, windDirection, precipitation, weatherCode) 2. forecast array (7 days with tempMin, tempMax, precipitation, weatherCode) 3. location (city, country, latitude, longitude) 4. timezone. Example output: {"location":{"city":"Paris","country":"France","latitude":48.85,"longitude":2.35},"current":{"temperature":18.5,"humidity":62,"windSpeed":12,"precipitation":0,"weatherCode":"partly_cloudy"},"forecast":[{"date":"2026-04-14","tempMin":12,"tempMax":20,"precipitation":0.2}]} Use this FOR travel planning, outdoor event scheduling, agriculture monitoring, logistics planning, and building weather-aware applications. Do NOT use for timezone info -- use utility_convert_timezone instead. Do NOT use for IP-based location -- use ip_lookup_geolocation instead. Do NOT use for stock data -- use finance_get_stock_price instead.
Input schema lacks parameter descriptions and type constraints. 'latitude' and 'longitude' parameters have only range hints in descriptions (e.g., '(-90 to 90)'), not actionable LLM guidance. 'city' parameter has no description at all. No enum, pattern, or format constraints present.
Required parameters array is empty despite latitude/longitude being mutually exclusive with city. LLMs cannot determine which parameter combinations are valid. Should declare either (latitude AND longitude) OR city as required, with mutual exclusivity documented.
Output schema is not documented in tool definition. Tool description includes example JSON output, but no formal schema is present. LLMs cannot reliably parse response structure or plan downstream operations without a documented schema.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2025-06-18+ | v2 |
Tool description embeds example output JSON inline. While helpful for humans, LLMs tend to reuse example values literally (e.g., 'Paris', '48.85') in real calls. Replace with formal output schema and remove example coordinates.
No error handling guidance documented. Tool description does not explain what happens on invalid coordinates, unknown cities, API failures, or rate limits. LLMs have no recovery path if a call fails.