Buienradar 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_precipitation_forC | Fetches precipitation data for the next 2 hours from Buienradar. |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming follows a clear verb_noun pattern (get_precipitation_for).
One tool is too few for a weather data server, as it severely limits functionality. A Buienradar server should ideally include tools for forecasts, radar images, or location-based queries, making this set incomplete and under-scoped.
The tool set is severely incomplete for a weather data domain. It only provides precipitation data for a short timeframe, with no coverage for forecasts, historical data, radar visuals, or other essential weather parameters, leading to significant gaps in functionality.