mcp-weather
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_noteC | Write a new note |
| query_weatherC | Query the weather |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tool_usage | Provides precise instructions for using the available tools |
| weather_tool_guide | Detailed guide for using the weather query tool |
| note_tool_guide | Detailed guide for using the note writing tool |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| First Note | This is note 1 |
| Second Note | This is note 2 |
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.