mcp-weather
Related Servers
Alternatives to mcp-weather
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes.23-
- AlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes.12559 npm3MIT
- AlicenseAqualityFmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes via URIs and tools.1210 npm8MIT
- FlicenseCqualityDmaintenanceA TypeScript-based MCP server implementing a simple notes system that allows users to create, access, and generate summaries of text notes.14 npm-
- FlicenseNot gradedqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system with resources, tools for creating notes, and prompts for summarization.-
- AlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of notes via Claude Desktop integration.25 npmISC
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: query_weather deals with weather data retrieval, while write_note handles note creation. There is no overlap or ambiguity between these unrelated functions, making misselection highly unlikely.
The tools use a consistent verb_noun pattern (query_weather, write_note), which is good. However, the server name 'mcp-weather' suggests a weather-focused domain, making write_note an outlier that breaks thematic consistency, though the naming style itself is uniform.
With only 2 tools, the set feels too thin for the implied scope. The server name indicates a weather domain, but write_note is unrelated, leaving weather functionality underdeveloped (e.g., no forecast, alerts, or location-based queries). This minimal count does not adequately cover the expected domain.
The tool surface is severely incomplete. For a weather server, basic operations like getting forecasts, historical data, or location searches are missing, and write_note is irrelevant to the domain. This creates significant gaps that will cause agent failures in weather-related tasks.