Swiss Meteo MCP
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add-noteC | Add a new note |
| get-temperatureC | Get the current temperature for a location using SwissMeteo APIs. |
| delete-all-notesB | Delete all notes from the server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The tools have unclear boundaries and overlapping purposes. 'add-note' and 'delete-all-notes' are related to note management, while 'get-temperature' is a weather API tool, creating a split domain. Within the note tools, there is a gap between adding and deleting all notes, but they are distinct from the weather tool, though the server name suggests a weather focus, making the note tools ambiguous in context.
The naming shows mixed conventions. 'add-note' and 'delete-all-notes' use kebab-case with verb-object patterns, while 'get-temperature' also uses kebab-case but is more descriptive. There is no consistent pattern across all tools, as the note tools imply a different domain than the weather tool, leading to readability issues.
With only 3 tools, the count is too few for the apparent scope. The server name 'Swiss Meteo MCP' suggests a weather-related service, but only one tool ('get-temperature') directly supports this, while the other two are for note management, creating an incomplete and mismatched set for the domain.
The tool surface is severely incomplete for the stated purpose. Based on the server name, weather-related operations are expected, but only 'get-temperature' is provided, missing other essential weather data (e.g., forecasts, humidity). The note tools are unrelated and lack full CRUD coverage (e.g., no update or individual delete), leading to significant gaps that will cause agent failures.