Skip to content
Eden Engine

San Mateo County Open Data: Dataset Metadata and Licence

smcgovopendata/dataset-metadata

Returns the metadata of one dataset on the San Mateo County open data portal by its dataset id: name, description, category, attribution, licence, and when the data and metadata were last updated. Use it to check a dataset's licence and freshness before querying its rows. An unknown dataset id returns a validation error. Passed through unmodified and served by Eden Engine; not an official County of San Mateo product.

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

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

// 2. inspect: price and input schema
omnial_inspect({ tool: "smcgovopendata/dataset-metadata" })

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

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

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "dataset_id"
  ],
  "properties": {
    "dataset_id": {
      "type": "string",
      "pattern": "^[a-z0-9]{4}-[a-z0-9]{4}$",
      "description": "The dataset's 8-character id, for example g5sj-6zp8. Find ids with the dataset catalog tool."
    }
  },
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "id",
    "name"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "name": {
      "type": "string"
    },
    "license": {
      "description": "The dataset's licence as the portal states it.",
      "additionalProperties": true
    },
    "category": {
      "type": [
        "string",
        "null"
      ]
    },
    "createdAt": {
      "type": "string"
    },
    "attribution": {
      "type": [
        "string",
        "null"
      ]
    },
    "description": {
      "type": [
        "string",
        "null"
      ]
    },
    "dataUpdatedAt": {
      "type": "string"
    },
    "metadataUpdatedAt": {
      "type": "string"
    }
  },
  "additionalProperties": true
}