Ontario Open Data: List Dataset IDs
ontariodatacatalogue/list-dataset-ids
Lists dataset ids (slugs) from the Ontario Data Catalogue in alphabetical order, a page at a time: about 1,000 datasets are released under the Open Government Licence – Ontario, the only ones listed. Pass an id to the dataset lookup for its full record. Data from the Ontario Data Catalogue, served by Eden Engine; not an official Government of Ontario product.
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
Dataset metadata from the Ontario Data Catalogue (data.ontario.ca), Government of Ontario. Contains information licensed under the Open Government Licence – Ontario; only datasets released under that licence are served, and each record names it in `license_id`. Passed through unmodified. Served by Eden Engine; not an official Government of Ontario 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: "ontariodatacatalogue/list-dataset-ids" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "ontariodatacatalogue/list-dataset-ids" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "ontariodatacatalogue/list-dataset-ids", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "ontariodatacatalogue/list-dataset-ids", 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": [
"limit"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "How many ids to return, 1 to 500. Required."
},
"offset": {
"type": "integer",
"minimum": 0,
"description": "How many ids to skip, to read the next page. Leave out to start at the first."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"count",
"results"
],
"properties": {
"count": {
"type": "integer",
"description": "How many datasets are listed in total."
},
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The dataset's slug, the id the dataset lookup takes."
}
},
"additionalProperties": true
},
"description": "One page of datasets in alphabetical order of slug."
}
},
"description": "The number of listed datasets and one page of their ids.",
"additionalProperties": true
}