IOOS Sensor Station Dataset Metadata (IOOS Sensors ERDDAP)
ioossensorserddap/get-dataset-info
The full metadata of one IOOS Sensors ERDDAP dataset: global attributes (title, institution, summary, licence, citation, geographic and time coverage) and every variable with its attributes and units, as ERDDAP's row-per-attribute table. The input is the Dataset ID from list-datasets or search-datasets. An unknown id is a validation error. Large stations return about 50 KB.
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/get-dataset-info" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "ioossensorserddap/get-dataset-info" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "ioossensorserddap/get-dataset-info", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "ioossensorserddap/get-dataset-info", 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": [
"datasetID"
],
"properties": {
"datasetID": {
"type": "string",
"pattern": "^[A-Za-z0-9_.-]{1,120}$",
"description": "An ERDDAP Dataset ID from list-datasets or search-datasets, for example ism-secoora-org_cormp_sun2 or gov_usgs_nwis_301204081434900."
}
},
"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": "One row per attribute: Row Type, Variable Name, Attribute Name, Data Type and Value. NC_GLOBAL rows describe the dataset as a whole."
},
"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
}