Loading ToolBench
Weather MCP server providing forecast data and weather information via National Weather Service API
Single tool 'get_forecast' has a clear action verb and proper JSON Schema with typed parameters (latitude, longitude as numbers). Description is present but minimal (11 words, 60 chars), below the 194-char baseline for production tools. No parameter descriptions visible in the schema, violating the requirement that every parameter must explain what it controls. No output schema documented. No error handling guidance. Tool is READ_ONLY (good), but lacks the depth expected for production use.
Get weather forecast for a given latitude and longitude.
Parameter descriptions missing. 'latitude' and 'longitude' have no descriptions explaining units (degrees?), valid ranges, or coordinate system (WGS84?). LLMs cannot infer these details from names alone.
Tool description is 60 characters, well below the 194-char baseline. Lacks context on when to use this tool, what format the forecast is in, or what geographic coverage is supported. Too terse for LLM selection.
Output schema not documented. LLMs cannot plan downstream operations or extract fields if they don't know what the response contains (temperature, precipitation, wind speed, etc.).
No error handling guidance. If coordinates are invalid, out of bounds, or the weather service is unavailable, the tool provides no recovery hints. LLMs cannot self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
No parameter constraints (min/max latitude/longitude). Unbounded numeric inputs let LLMs pass invalid coordinates (e.g., latitude 999) that will fail at runtime.