Skip to main content
Glama
wolkwork

KNMI Weather MCP

by wolkwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KNMI_API_KEYYesYour API key from KNMI Data Platform

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_location_weatherC

Get current weather data for a location

search_locationC
Search for locations in the Netherlands

Args:
    query: Search term for location
get_nearest_stationB
Find the nearest KNMI weather station to given coordinates

Args:
    latitude: Latitude in degrees
    longitude: Longitude in degrees
what_is_the_weather_like_inB
Get and interpret weather data for a location in the Netherlands

Args:
    location: City or place name in the Netherlands
Returns:
    A natural language interpretation of the current weather conditions

Prompts

Interactive templates invoked by user choice

NameDescription
weather_interpretationHelp Claude interpret raw weather data

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

Tools are mostly distinct: search_location and get_nearest_station are clearly supporting, but get_location_weather and what_is_the_weather_like_in both provide current weather, albeit in different formats (data vs. natural language). This overlap could cause misselection.

Naming Consistency3/5

Three tools follow verb_noun pattern (get_location_weather, get_nearest_station, search_location), but what_is_the_weather_like_in deviates entirely into a conversational question, breaking consistency.

Tool Count5/5

With 4 tools, the server is well-scoped for a focused weather service covering location search, station lookup, and current conditions. Each tool serves a clear purpose without being excessive.

Completeness3/5

The tool set covers location search and current weather but lacks forecast, historical data, or station metadata. The domain of weather for the Netherlands has notable gaps that could hinder some agent tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources