RDW 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 |
|---|---|
| rdw-license-plate-lookupB | Look up ALL available Dutch vehicle information from RDW databases including vehicle specs, fuel/emissions, APK history, recalls, ownership history, technical defects, and more |
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 descriptive verb-noun pattern (rdw-license-plate-lookup).
A single tool is too few for a server that claims to provide comprehensive vehicle information, as it forces all functionality into one monolithic tool. This limits flexibility and may cause issues for agents needing specific operations.
The tool description suggests broad coverage, but a single tool is insufficient for a complete domain surface. There are likely gaps in operations (e.g., no separate tools for updates, deletions, or specialized queries), making it incomplete for the stated purpose.