aadt_layers
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_layers for the schema, then POST the same URL with its arguments for the data.
Which FHWA HPMS data years exist for a US state and which columns each year carries (the newest years drop route number/name columns), so callers can pick a year before querying.
Example call
Arguments
{
"state": "VT"
}
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_layers","arguments":{"state":"VT"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('aadt_layers', {
"state": "VT"
});
Response shape
| Field | Type | Description |
|---|---|---|
state | string | |
source | string | |
data_year | number | |
data_as_of | string | |
years_available | array | |
layers | array | |
caveat | string |
Full JSON Schema
{
"type": "object",
"properties": {
"state": {
"type": "string"
},
"source": {
"type": "string"
},
"data_year": {
"type": "number"
},
"data_as_of": {
"type": "string"
},
"years_available": {
"type": "array",
"items": {
"type": "number"
}
},
"layers": {
"type": "array",
"items": {
"type": "object",
"properties": {
"data_year": {
"type": "number"
},
"has_route_number_and_name": {
"type": "boolean"
},
"returned_columns": {
"type": "array",
"items": {
"type": "string"
}
},
"column_count": {
"type": "number"
}
},
"additionalProperties": true
}
},
"caveat": {
"type": "string"
}
},
"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.