A general-purpose MCP (Model Context Protocol) server written in Go that provides calculator, network, and weather tools with real-time data access.
LazyMCP has 5 tools with clear naming and mostly adequate descriptions. All tools follow verb_noun conventions (get_*, calculate). Schemas are present and structured using the mcp-go framework. However, parameter descriptions lack specificity about constraints and formats, output schemas are not documented, and error handling is minimal. The tools are mostly READ_ONLY utility functions (calculator, IP lookup, weather), which limits composition complexity.
Evaluate mathematical expressions using natural syntax (e.g., '2 + 3 * 4', 'sin(pi/4)', 'sqrt(16)')
Get the IP address of the client making the request
Get detailed information about the client's IP address including geolocation data
Get current weather for a location. Uses client's IP location by default, or accepts a custom location parameter (city name or 'lat,lon' coordinates)
Get 5-day weather forecast for a location. Uses client's IP location by default, or accepts a custom location parameter (city name or 'lat,lon' coordinates)
Output schemas not documented. While input schemas are well-structured, tool responses (e.g., what fields does get_ip_data return?) are not formally documented in code or inline. LLMs cannot plan downstream calls without knowing response structure.
get_ip tool description is too brief ('Get the IP address of the client making the request'). It lacks context on WHEN to use it vs get_ip_data, whether it requires network access, or what format the response is in.
Parameter descriptions for location/ip fields include example values ('London', '40.7128,-74.0060'). Per the rubric, examples should be replaced with formal constraints (enum, format, pattern). LLMs may reuse example coordinates literally instead of adapting to user intent.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 47 | - | v1 |
No error handling guidance. Tools return simple text results but do not specify what happens on invalid input (e.g., malformed expression, invalid IP, unknown location). LLMs receive no recovery hints and cannot self-correct.
Tool descriptions lack differentiation. get_ip and get_ip_data are two separate tools, but descriptions do not explain WHEN to call one vs the other. 'Get the IP address' vs 'Get detailed information about the IP' is ambiguous, the LLM may waste a call trying both.