GitHub: jongkwang/hello-mcp-server-python
Two tools with minimal descriptions (both under 50 chars) and incomplete parameter documentation. calculate_bmi has no parameter descriptions at all; fetch_weather lacks error handling guidance and does not document the response format. Neither tool documents output schemas. No error recovery patterns, no input validation guidance, and no security considerations (fetch_weather makes external HTTP calls without timeout/retry documentation). Naming is acceptable (verb_noun pattern), but descriptions fall well below the 194-char baseline for production tools.
Calculate BMI given weight in kg and height in meters
Fetch current weather for a city
Parameter descriptions missing entirely. calculate_bmi parameters (weight_kg, height_m) and fetch_weather parameter (city) lack descriptions explaining units, constraints, or valid ranges. LLMs cannot infer that height_m expects meters, not feet.
Output schemas not documented. Neither tool specifies what type or structure is returned. calculate_bmi returns a float; fetch_weather returns a string. LLMs need explicit return type documentation to plan downstream operations.
fetch_weather makes external HTTP calls without documented error handling, timeouts, or recovery guidance. No indication of what happens on network failure, invalid city, or API rate limits. Agents cannot self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Tool descriptions are too brief (35 and 30 chars vs. 194-char baseline). 'Calculate BMI given weight in kg and height in meters' lacks context on when to use this tool or what the output represents. 'Fetch current weather for a city' does not explain response format or error cases.
No input validation or constraint documentation. calculate_bmi accepts any float; no guidance on valid ranges (e.g., height > 0, weight > 0). fetch_weather accepts any string; no guidance on city name format or length limits.