EMODnet Marine Datasets List (EMODnet ERDDAP)

emodneterddap/list-datasets

One page of the datasets held by the EMODnet ERDDAP server (European Marine Observation and Data Network): bathymetry, seabed habitats, marine biology, chemistry and physics analyses, with title, summary, institution and griddap or tabledap access paths. 1 to 20 datasets per page, in the server's order. The catalogue held 145 pages at 3 per page on 2026-10-20.

activeper callv1

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 $5.

Data source

EMODnet

Data from EMODnet (European Marine Observation and Data Network, https://emodnet.ec.europa.eu/), owned by the EU and licensed under CC BY 4.0 unless a dataset's own metadata (license, citation, acknowledgement) says otherwise; credit the originator named in that metadata. Served by Eden Engine; not an official EMODnet 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.

Install it Create an account

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "emodneterddap/list-datasets" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "emodneterddap/list-datasets" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "emodneterddap/list-datasets", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "emodneterddap/list-datasets", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not 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

input_schema.json

{
  "type": "object",
  "required": [
    "page",
    "itemsPerPage"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 1000,
      "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

output_schema.json

{
  "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 griddap or 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
}