Skip to main content
Glama
enesjakozh
wpnbos

Buienradar MCP Server

by wpnbos
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Buienradar MCP Server

Overview

This is an MCP server that fetches precipitation data for a given latitude and longitude using Buienradar. It exposes a single MCP tool, get_precipitation_for, which provides precipitation forecasts for the next two hours.

Installing via Smithery

To install Buienradar MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @wpnbos/buienradar-mcp-server --client claude

Related MCP server: Buienradar MCP Server

Configuration

First, make sure you have uv (and Python) installed.

To integrate this server with Claude for Desktop, update your configuration file at:

MacOS/Linux

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

code $env:AppData\Claude\claude_desktop_config.json

Example configuration:

{
    "mcpServers": {
        "precipitation": {
            "command": "uv",
            "args": [
                "--directory",
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/buienradar-mcp-server",
                "run",
                "server.py"
            ]
        }
    }
}

Replace /ABSOLUTE/PATH/TO/PARENT/FOLDER/buienradar-mcp-server with the actual path where your server is located.

Restart Claude for Desktop for the tool to become available.

You might have to provide the full path for uv instead of just uv. To find the full path for your uv executable, on MacOS/Linux execute which uv.

Usage

If all went well, you should be able to ask Claude about any upcoming precipitation.

> Will there be any rain soon in Amsterdam?

> No rain predicted in Amsterdam for the next 2 hours.

Available Tools

1 tool
get_precipitation_forC

Fetches precipitation data for the next 2 hours from Buienradar.

ParametersJSON Schema
NameRequiredDescriptionDefault
latYes
lonYes

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states it fetches data without disclosing behavioral traits like rate limits, authentication needs, data freshness, error conditions, or response format. It mentions the source (Buienradar) but not what that implies for reliability or availability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste—it directly states the tool's function, time scope, and data source. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on parameters, return values, error handling, and operational constraints, which are critical for a data-fetching tool with required inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about the parameters (lat, lon). It doesn't explain what these represent (latitude/longitude coordinates), valid ranges, units, or how they affect the data fetched, leaving parameters completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetches precipitation data') and resource ('from Buienradar'), with specific time scope ('for the next 2 hours'). It doesn't need to differentiate from siblings since none exist, but could be more specific about what precipitation data includes (e.g., rainfall intensity, probability).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives or prerequisites. The description mentions the data source (Buienradar) but doesn't explain limitations or appropriate contexts for use, leaving the agent without operational context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedget_precipitation_for
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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).

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wpnbos/buienradar-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server