Skip to content
Eden Engine
Get started

EMODnet Dataset Metadata (EMODnet ERDDAP)

emodneterddap/get-dataset-info

The full metadata of one EMODnet ERDDAP dataset by Dataset ID: its variables and dimensions and every global attribute, including title, summary, institution, creator, licence, citation and acknowledgement, and the geographic and time coverage. Use the licence and citation rows to credit the originator.

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 itCreate an account
agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "emodneterddap/get-dataset-info" })

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

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "emodneterddap/get-dataset-info", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "emodneterddap/get-dataset-info", 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.

ChargePrice
Per call
$0.0026
Updated
Oct 21, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "datasetID"
  ],
  "properties": {
    "datasetID": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_]{1,80}$",
      "description": "An ERDDAP Dataset ID from list-datasets or search-datasets, for example biology_8777_429f_a47a_d420 or emodnet_bathy_2018_full."
    }
  },
  "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": "One attribute per row: Row Type, Variable Name (NC_GLOBAL for dataset-wide), Attribute Name, Data Type, Value."
        },
        "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
}