List of Finnish Road Traffic Measuring Stations with Coordinates (Digitraffic)
digitrafficroad/road-stations
The Finnish road traffic measuring stations (TMS) that are currently collecting data (about 450): for each the station id the road-station-data tool takes, the station number, its name and latitude and longitude. Stations that are removed or not gathering are left out. Use the coordinates to find the station nearest a place. Takes no input. Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Modified by Eden Engine (fields renamed and reduced). Served by Eden Engine; not an official Fintraffic product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY (https://creativecommons.org/licenses/by/4.0/). Modified by Eden Engine (fields renamed and reduced). Served by Eden Engine; not an official Fintraffic product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "digitrafficroad/road-stations" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "digitrafficroad/road-stations" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "digitrafficroad/road-stations", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "digitrafficroad/road-stations", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 27, 2026
Input and output schemas
Input schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"count",
"stations"
],
"properties": {
"count": {
"type": "integer",
"description": "Stations in the answer (at most 600)."
},
"stations": {
"type": "array",
"items": {
"type": "object",
"required": [
"stationId"
],
"properties": {
"name": {
"type": [
"string",
"null"
],
"description": "Station name or code."
},
"latitude": {
"type": [
"number",
"null"
],
"description": "Latitude in degrees."
},
"longitude": {
"type": [
"number",
"null"
],
"description": "Longitude in degrees."
},
"stationId": {
"type": "integer",
"description": "Station id for the road-station-data tool."
},
"tmsNumber": {
"type": [
"integer",
"null"
],
"description": "Station number on the road."
}
},
"additionalProperties": false
},
"description": "Stations that are collecting data."
}
},
"additionalProperties": false
}