Loading ToolBench
MCP server that provides real-time weather data to Claude. Integrates with OpenWeatherMap API to retrieve and process weather information.
Weather MCP server has well-structured tool definitions with complete input schemas and reasonable descriptions. All 5 tools follow verb_noun naming (get_*, compare_*). Schemas include proper types, enums, and constraints (e.g., days 1-5, units enum). However, descriptions are generic and lack actionable context for LLM selection. No output schemas documented. Error handling is minimal, generic 'Could not find weather data' messages don't guide recovery. Missing parameter descriptions for some fields (e.g., 'lat'/'lon' lack format hints). No tool annotations (readOnlyHint present via Risk field but not in MCP schema). Composition is sound, each tool has single responsibility.
Compare weather conditions between two locations side-by-side
Get current weather information including temperature, feels_like, humidity, description, and wind_speed
Get weather forecast with daily highs/lows for specified number of days
Get severe weather warnings and alerts for a location if any exist
Get current weather for specific latitude and longitude coordinates
No output schemas documented. LLMs cannot plan downstream calls or extract fields without knowing response structure (e.g., what fields does get_current_weather return?).
Descriptions lack actionable context. 'Get current weather information...' is generic; should explain WHEN to use this vs get_weather_by_coords, what data is returned, and any prerequisites (e.g., 'Requires valid city name; returns temp, humidity, wind_speed, description').
Error handling is minimal and non-actionable. Generic messages like 'Could not find weather data for {location}' don't guide recovery. Should suggest alternatives: 'Location not found. Try a different city name or use get_weather_by_coords with latitude/longitude.'
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
Coordinate parameters (lat, lon) lack format hints. Descriptions should specify range (-90 to 90 for lat, -180 to 180 for lon) and precision expectations to prevent invalid API calls.
No tool annotations in MCP schema. Tools are read-only but lack readOnlyHint in inputSchema. This prevents clients from optimizing caching or safety policies.