San Mateo County Open Data: Dataset Catalog (data.json)
smcgovopendata/list-datasets
Returns the catalog of public datasets on the San Mateo County open data portal (data.smcgov.org): for each dataset its title, description, keywords, issued and modified dates, publisher, landing page and download links. The last part of each identifier is the dataset id used by the rows and metadata tools. Takes no input and returns the whole catalog (about 50 datasets). Passed through unmodified and served by Eden Engine; not an official County of San Mateo 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
San Mateo County Open Data (data.smcgov.org)
Data from the County of San Mateo, published on Open San Mateo County (data.smcgov.org). Each dataset's metadata names its publishing department and licence. Served by Eden Engine; not an official County of San Mateo 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: "smcgovopendata/list-datasets" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "smcgovopendata/list-datasets" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "smcgovopendata/list-datasets", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "smcgovopendata/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 24, 2026
Input and output schemas
Input schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"dataset"
],
"properties": {
"dataset": {
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string"
},
"issued": {
"type": "string"
},
"keyword": {
"type": "array",
"items": {
"type": "string"
}
},
"modified": {
"type": "string"
},
"identifier": {
"type": "string",
"description": "The dataset's API address; its last path segment is the dataset id."
},
"description": {
"type": "string"
},
"landingPage": {
"type": "string"
},
"distribution": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
}
}
},
"additionalProperties": true
},
"description": "One entry per public dataset."
}
},
"description": "The portal's DCAT catalog.",
"additionalProperties": true
}