anwb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANWB_TOOLSETS | No | Comma-separated list of tool categories to enable (locations, routes, incidents). Default: all toolsets. | |
| ANWB_CACHE_TTL | No | Cache TTL in seconds (set to 0 to disable). Routes/incidents use 60s, locations use 300s. | unset |
| ANWB_MAX_RETRIES | No | Maximum retry attempts for rate-limited (429) requests with exponential backoff. | 3 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_locationsA | Search for locations, addresses, streets, cities, and points of interest in the Netherlands and surrounding countries. Returns matching locations with coordinates, useful for route planning. Use this to find coordinates for the calculate_route tool. |
| calculate_routeA | Calculate a route between two or more locations using ANWB route planning. Supports car, caravan, bike, and pedestrian modes. Provide locations as latitude,longitude pairs separated by colons (e.g. '52.37,4.89:51.44,5.47'). Returns distance, duration, turn-by-turn directions, toll information (car/caravan only), and optional alternative routes. Use find_locations first to get coordinates for place names. |
| calculate_ev_routeA | Calculate an electric vehicle route between two or more locations using ANWB EV route planning. Requires an EV car model ID, battery capacity, and current state of charge. Returns distance, duration, battery consumption, charging stops (if needed), and nearby charging stations. Provide locations as latitude,longitude pairs separated by colons. Use find_locations first to get coordinates for place names. |
| list_ev_carsA | List available electric vehicle models from the ANWB database. Returns car IDs, make, model, version, and battery information. Use the car ID with calculate_ev_route to plan an EV route. Optionally filter by make (brand) or search by model name. |
| get_traffic_incidentsA | Get current traffic incidents on Dutch highways from ANWB. Returns jams, road closures, roadworks, and speed camera locations. Optionally filter by road (e.g. 'A1', 'A2') and/or category (jams, roadworks, radars). |
| get_traffic_summaryA | Get a compact summary of current traffic conditions on Dutch highways. Returns total counts of jams, road closures, roadworks, and radars across all highways. |
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 6 tools
Each tool has a clearly distinct role: traffic summary versus detailed incidents, standard route versus EV route, plus supporting lookup tools for locations and EV cars. Although get_traffic_summary and get_traffic_incidents both cover traffic, one provides aggregate counts and the other detailed filters, so there is no real ambiguity.
All tool names follow a consistent snake_case verb_noun pattern: get_, find_, calculate_, and list_. The naming clearly communicates both the action and the resource, with calculate_route and calculate_ev_route sharing a predictable structure.
Six tools is well-scoped for an ANWB mobility server covering traffic conditions, location search, standard route planning, and EV route planning. Each tool serves a distinct purpose and none feel redundant or unnecessary.
The tool surface covers the full workflow: find locations, get traffic context, calculate both standard and EV routes, and look up EV car models for route planning. There are no obvious dead ends or missing operations for the stated domain.