Sample MCP server providing weather information tools
Server provides two tools with complete input schemas and descriptions. Tool naming follows verb_noun convention (get_weather, get_forecast). Descriptions exist and are actionable (10 - 50 chars, below ideal 50 - 200 char range). Parameters are typed with enums for units. However, descriptions lack detail about when to use each tool, what constitutes valid input, and error recovery guidance. Output schemas are undocumented, LLMs cannot plan downstream operations or extract structured fields reliably. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Error handling returns text but lacks recovery guidance ('Error: Missing "city" argument' does not suggest what to do next). Resources and prompts are implemented but minimal in scope.
Get 5-day weather forecast for a city
Get current weather information for a city
Tool descriptions lack context for LLM selection. 'Get current weather information for a city' (49 chars) does not explain when to use get_weather vs get_forecast, what the difference is, or what fields are returned.
Output schemas are completely undocumented. Tools return unstructured text responses (see CallToolRequestSchema handler returning text-only content). LLMs cannot parse structured fields or plan multi-step operations. Baseline: 100% of A+ tools document return types.
No tool annotations present. Tools lack readOnlyHint (both are read-only), destructiveHint, or idempotentHint. Current spec (2026-07-28) expects tools to declare their side-effect profile via annotations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 56 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 59 | - | v1 |
Error messages provide no recovery guidance. 'Error: Missing "city" argument' does not suggest calling a discovery tool or what format city names accept. Baseline: error responses must tell the LLM what to do next.
Parameter descriptions are minimal. 'The city name to get weather for' (29 chars) does not specify format (e.g., 'English city name, e.g. New York'), constraints (max length, special character handling), or what happens if the city is not found.