aadt_top_segments
Pack: hpms-aadt · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/aadt_top_segments for the schema, then POST the same URL with its arguments for the data.
The busiest road segments in a US state by AADT (annual average daily traffic), optionally within one county or functional class (1 Interstate … 7 Local). From FHWA HPMS; per roadway section as reported by the state. Also the way to learn a state’s route_id naming style.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
county | number | no | Optional state-coded county_id (county FIPS code). |
f_system | number | no | Optional functional system 1-7: 1 Interstate, 2 other freeway, 3 other principal arterial, 4 minor arterial, 5 major collector, 6 minor collector, 7 local. |
Example call
Arguments
{
"state": "TX",
"f_system": 1,
"limit": 5
}
curl
curl -X POST https://gateway.pipeworx.io/hpms-aadt/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"aadt_top_segments","arguments":{"state":"TX","f_system":1,"limit":5}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('aadt_top_segments', {
"state": "TX",
"f_system": 1,
"limit": 5
});
Response shape
| Field | Type | Description |
|---|---|---|
state | string | |
data_year | number | |
data_as_of | string | |
source | string | |
caveat | string | |
total_matching | number | |
returned | number | |
truncated | boolean | |
narrowing_hint | string | |
segments | array |
Full JSON Schema
{
"type": "object",
"properties": {
"state": {
"type": "string"
},
"data_year": {
"type": "number"
},
"data_as_of": {
"type": "string"
},
"source": {
"type": "string"
},
"caveat": {
"type": "string"
},
"total_matching": {
"type": "number"
},
"returned": {
"type": "number"
},
"truncated": {
"type": "boolean"
},
"narrowing_hint": {
"type": "string"
},
"segments": {
"type": "array",
"items": {
"type": "object",
"properties": {
"route_id": {
"type": "string"
},
"f_system": {
"type": "number"
},
"aadt": {
"type": "number"
},
"aadt_single_unit": {
"type": "number"
},
"aadt_combination": {
"type": "number"
},
"county_id": {
"type": "number"
},
"begin_point": {
"type": "number"
},
"end_point": {
"type": "number"
},
"data_year": {
"type": "number"
},
"speed_limit": {
"type": "number"
},
"through_lanes": {
"type": "number"
},
"urban_id": {
"type": "number"
},
"ownership": {
"type": "number"
},
"f_system_name": {
"type": "string"
}
},
"additionalProperties": true
}
}
},
"additionalProperties": true
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the hpms-aadt pack
{
"mcpServers": {
"hpms-aadt": {
"url": "https://gateway.pipeworx.io/hpms-aadt/mcp"
}
}
}
See Getting Started for client-specific install steps.