KNMI MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Get current weather information for a Dutch location. The location parameter accepts location names (e.g., 'Amsterdam', 'De Bilt') and automatically converts them to the required grid identifiers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'get_weather' has a clear and distinct purpose, making disambiguation trivial.
The single tool name 'get_weather' follows a clear verb_noun pattern (get + weather). Since there is only one tool, consistency is inherently perfect with no deviations to evaluate.
A single tool is too few for a weather server's apparent scope, which typically involves multiple operations like forecasts, historical data, or alerts. This minimal set limits functionality and feels incomplete for the domain.
The tool set is severely incomplete for a weather server, covering only current weather retrieval. Obvious gaps include forecasts, historical data, alerts, or multi-location queries, which are essential for comprehensive weather-related tasks.