aria-mcp-trafik-dk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VD_GCS_BASE | No | Override the GCS base URL (for testing or caching proxies). | https://storage.googleapis.com/trafikkort-data/geojson |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| traffic_eventsA | Fetch current Danish road traffic events from Vejdirektoratet (trafikkort.vejdirektoratet.dk). Returns incidents, accidents, roadblocks, queues, and closures on Danish state roads. Each event includes type, road, location, description, from/to times, and severity. Use this to warn ARIA before Kim drives — check for incidents on the route. Data is updated approximately every 3 minutes. |
| roadworksA | Fetch planned and ongoing roadworks on Danish state roads from Vejdirektoratet. Combines two feeds: active roadwork layers from the live events feed and critical-announcements.json (major planned closures, e.g. motorway bridge work). Returns roadwork entries with title, description, road, location, and validity times. Use this when ARIA needs to warn about scheduled disruptions before a drive. |
| events_nearA | Find current traffic events (incidents, roadblocks, queues, roadworks) within a geographic radius of a given coordinate. Useful for checking conditions near a specific destination or along a route. Only events that carry Point geometry from Vejdirektoratet are returned; events without coordinates are excluded. Results are sorted by distance ascending. Example: check for issues near Horsens (55.86, 9.85) before driving there. |
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 3 tools
Tools have overlapping purposes (events_near and traffic_events both return current events), but descriptions clarify differences: events_near is location-based, traffic_events is general. roadworks is distinct. Overall, agents likely select correctly with clear prompts.
Tool names lack a consistent pattern: 'events_near' combines noun+preposition, 'roadworks' is a single noun, 'traffic_events' is noun_noun. No verb_noun or consistent convention, making predictions harder.
Three tools is a reasonable count for querying Danish road events. It covers current incidents, planned roadworks, and proximity search without unnecessary duplication, though slightly minimalist.
Covers the main needs: current events globally and by location, and planned roadworks. Missing features like event details by ID or historical data, but sufficient for real-time trip planning.