IOOS Sensor Station Datasets List (IOOS Sensors ERDDAP)
ioossensorserddap/list-datasets
One page of the datasets held by the IOOS Sensors ERDDAP server: coastal, Great Lakes and river observing stations from the regional associations of the U.S. Integrated Ocean Observing System, with title, summary, institution and tabledap access paths. 1 to 20 datasets per page, in the server's order. The catalogue held about 29,000 datasets on 2026-10-20, so use search-datasets to find a station by name or variable.
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
Data from the IOOS Sensors ERDDAP server (https://erddap.sensors.ioos.us/erddap/), which aggregates observations from the regional associations of the U.S. Integrated Ocean Observing System and other data providers. Each dataset names its institution and licence in its own metadata; credit the institution named there. Served by Eden Engine; not an official IOOS 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: "ioossensorserddap/list-datasets" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "ioossensorserddap/list-datasets" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "ioossensorserddap/list-datasets", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "ioossensorserddap/list-datasets", 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 21, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"page",
"itemsPerPage"
],
"properties": {
"page": {
"type": "integer",
"maximum": 10000,
"minimum": 1,
"description": "The results page, starting at 1. A page past the last one is refused by the upstream."
},
"itemsPerPage": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "Datasets per page, 1 to 20."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"table"
],
"properties": {
"table": {
"type": "object",
"required": [
"columnNames",
"rows"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": [
"string",
"number",
"null"
]
}
},
"description": "Each row is one dataset; the Dataset ID is the last column, and the columns give title, summary, institution and the tabledap access paths."
},
"columnNames": {
"type": "array",
"items": {
"type": "string"
},
"description": "Column names."
},
"columnTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Column types, parallel to columnNames."
}
},
"description": "ERDDAP's table grid: columnNames names the columns and every row is an array in that order.",
"additionalProperties": true
}
},
"additionalProperties": true
}