MCP server providing weather alerts, weather forecasts, and stock price information
Three tools present with basic naming and descriptions, but significant quality gaps. All tools are properly registered with @mcp.tool() decorators and have input schemas visible in source. However, descriptions are minimal and parameter descriptions lack specificity. Output schemas are not documented. Error handling is minimal. The tools are read-only (no destructive operations), but lack the documentation and structure expected of production-grade tools. Average tool score: 48 (get_stockprice: 47, get_alerts: 49, get_forecast: 48).
Get weather alerts for a US state.
Get weather forecast for a location.
Fetch stock price information for a given ticker symbol, including current price, low price, high price, opening price, and link to Yahoo Finance.
Output schemas not documented. Tools return JSON strings or plain text without declaring the structure of returned fields. LLMs cannot plan downstream tool calls or extract required data reliably.
Parameter descriptions lack format and constraint details. 'ticker_symbol' parameter has minimal guidance ('Stock ticker symbol (e.g., AAPL, GOOGL)' includes example values which LLMs tend to reuse literally). State parameter format explicitly without examples, or use enums.
Tool descriptions are under 100 characters and lack context on WHEN to use each tool, WHAT it returns, and any prerequisites. Baseline for A+ tools is 194 chars avg. get_alerts and get_forecast descriptions are under 20 words each.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 45 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 50 | - | v1 |
Error handling is minimal and non-instructional. Errors return bare strings like 'Unable to fetch alerts or no alerts found' with no guidance on what the LLM should do next (retry, call a discovery tool, ask user). Pattern requires 'recovery guide' classification.
get_stockprice returns JSON with inconsistent/unclear field names ('current price' vs 'opening price', human-readable but non-standard). Baseline expects consistent snake_case or structured fields with type annotations.
state parameter in get_alerts accepts free-form strings with only a mention of 'Two-letter US state code (e.g. CA, NY)'. Should declare as enum of valid 2-letter state codes to prevent hallucinated values.