mcp-sam-gov

socrata_discover_datasets

Read-only

Search Socrata open data catalogs by topic keyword to locate dataset IDs. Optionally scope to a specific government portal, then use the returned ID with socrata_query.

Instructions

Find Socrata dataset 4x4 ids by keyword via the Socrata catalog (keyless, api.us.socrata.com). Input q (e.g. 'procurement', 'vendor payments'), optional domain (scope to one allowlisted portal; omit to search the whole allowlist), limit (≤100, def 20). Returns [{ id, name, description, domain, updatedAt, link }] + totalAvailable = the catalog resultSetSize. Feed a result's id to socrata_query as datasetId. NOTE: the federated catalog does not index every allowlisted host (e.g. USAC E-rate) — those stay queryable via socrata_query with a known 4x4.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	TOPIC words only, e.g. 'solicitations', 'contract', 'vendor payments', 'checkbook'. Put the JURISDICTION in `domain`, never in q: every q term must match and dataset titles rarely repeat their place name, so q='Illinois solicitations' returns 0 while domain=data.illinois.gov q='solicitations' finds the dataset.
`limit`	No	Max datasets to return, 1..100, default 20.
`domain`	No	Optional: scope discovery to ONE portal; omit to search all. The catalog does not index every host (USAC returns 0); those stay queryable via socrata_query with a known 4x4. Jurisdiction of non-obvious hosts: cthru.data.socrata.com=MASSACHUSETTS statewide (CTHRU); atlanta.data.socrata.com=Atlanta GA; controllerdata.lacity.org+data.lacity.org=Los Angeles; www.dallasopendata.com=Dallas TX; data.brla.gov=Baton Rouge LA; data.kcmo.org=Kansas City MO; data.cstx.gov=College Station TX; data.weho.org=West Hollywood CA; opendata.usac.org+datahub.usac.org=federal USAC E-rate. data.colorado.gov's procurement data is CITY OF DENVER, not CO state.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.16.0Sep 23, 2026

changedInput schema / properties / domain / description

Previous value: -"Optional: scope discovery to ONE allowlisted portal. Omit to search the whole allowlist. NOTE: the federated catalog does not index every host (e.g. USAC E-rate returns 0) — those remain queryable via socrata_query with a known 4x4."New value: +"Optional: scope discovery to ONE portal; omit to search all. The catalog does not index every host (USAC returns 0); those stay queryable via socrata_query with a known 4x4. Jurisdiction of non-obvious hosts: cthru.data.socrata.com=MASSACHUSETTS statewide (CTHRU); atlanta.data.socrata.com=Atlanta GA; controllerdata.lacity.org+data.lacity.org=Los Angeles; www.dallasopendata.com=Dallas TX; data.brla.gov=Baton Rouge LA; data.kcmo.org=Kansas City MO; data.cstx.gov=College Station TX; data.weho.org=West Hollywood CA; opendata.usac.org+datahub.usac.org=federal USAC E-rate. data.colorado.gov's procurement data is CITY OF DENVER, not CO state."

changedInput schema / properties / domain / enum

Previous value: -[
-  "data.ny.gov",
-  "data.colorado.gov",
-  "data.ct.gov",
-  "data.texas.gov",
-  "data.wa.gov",
-  "opendata.maryland.gov",
-  "data.vermont.gov",
-  "data.nj.gov",
-  "data.oregon.gov",
-  "data.pa.gov",
-  "data.mo.gov",
-  "data.delaware.gov",
-  "data.austintexas.gov",
-  "data.kingcounty.gov",
-  "data.montgomerycountymd.gov",
-  "data.mesaaz.gov",
-  "data.cambridgema.gov",
-  "data.transportation.gov",
-  "data.cdc.gov",
-  "data.bts.gov",
-  "datacatalog.cookcountyil.gov",
-  "data.illinois.gov",
-  "data.cincinnati-oh.gov",
-  "data.cityofnewyork.us",
-  "data.cityofchicago.org",
-  "data.sfgov.org",
-  "controllerdata.lacity.org",
-  "opendata.usac.org",
-  "data.kcmo.org",
-  "data.brla.gov",
-  "www.dallasopendata.com",
-  "data.lacity.org",
-  "data.ramseycountymn.gov",
-  "data.richmondgov.com",
-  "opendata.howardcountymd.gov",
-  "data.providenceri.gov",
-  "fiscalfocus.pittsburghpa.gov",
-  "data.coloradosprings.gov",
-  "data.framinghamma.gov",
-  "data.fultoncountyga.gov",
-  "atlanta.data.socrata.com",
-  "opendata.cityofmesquite.com",
-  "datahub.usac.org",
-  "performance.ci.janesville.wi.us",
-  "datahub.austintexas.gov",
-  "cthru.data.socrata.com",
-  "data.macoupincountyil.gov",
-  "data.oaklandca.gov",
-  "data.princegeorgescountymd.gov",
-  "data.cstx.gov",
-  "datahub.transportation.gov",
-  "citydata.mesaaz.gov",
-  "data.weho.org"
-]New value: +[
+  "data.ny.gov",
+  "data.colorado.gov",
+  "data.ct.gov",
+  "data.texas.gov",
+  "data.wa.gov",
+  "opendata.maryland.gov",
+  "data.vermont.gov",
+  "data.nj.gov",
+  "data.oregon.gov",
+  "data.pa.gov",
+  "data.mo.gov",
+  "data.delaware.gov",
+  "data.austintexas.gov",
+  "data.kingcounty.gov",
+  "data.montgomerycountymd.gov",
+  "data.mesaaz.gov",
+  "data.cambridgema.gov",
+  "data.transportation.gov",
+  "data.cdc.gov",
+  "data.bts.gov",
+  "datacatalog.cookcountyil.gov",
+  "data.illinois.gov",
+  "data.cincinnati-oh.gov",
+  "data.cityofnewyork.us",
+  "data.cityofchicago.org",
+  "data.sfgov.org",
+  "data.sf.gov",
+  "controllerdata.lacity.org",
+  "opendata.usac.org",
+  "data.kcmo.org",
+  "data.brla.gov",
+  "www.dallasopendata.com",
+  "data.lacity.org",
+  "data.ramseycountymn.gov",
+  "data.richmondgov.com",
+  "opendata.howardcountymd.gov",
+  "data.providenceri.gov",
+  "fiscalfocus.pittsburghpa.gov",
+  "data.coloradosprings.gov",
+  "data.framinghamma.gov",
+  "data.fultoncountyga.gov",
+  "sharefulton.fultoncountyga.gov",
+  "atlanta.data.socrata.com",
+  "opendata.cityofmesquite.com",
+  "datahub.usac.org",
+  "performance.ci.janesville.wi.us",
+  "datahub.austintexas.gov",
+  "cthru.data.socrata.com",
+  "data.macoupincountyil.gov",
+  "data.oaklandca.gov",
+  "data.princegeorgescountymd.gov",
+  "data.cstx.gov",
+  "datahub.transportation.gov",
+  "citydata.mesaaz.gov",
+  "data.weho.org"
+]

changedInput schema / properties / q / description

Previous value: -"Keyword(s) to find datasets, e.g. 'procurement', 'vendor payments', 'checkbook'."New value: +"TOPIC words only, e.g. 'solicitations', 'contract', 'vendor payments', 'checkbook'. Put the JURISDICTION in `domain`, never in q: every q term must match and dataset titles rarely repeat their place name, so q='Illinois solicitations' returns 0 while domain=data.illinois.gov q='solicitations' finds the dataset."

Addedv1.12.0Jul 27, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and openWorldHint annotations, the description reveals key behavior: the catalog is keyless, returns a specific object shape plus totalAvailable from resultSetSize, and does not index every allowlisted host. It also documents q-matching semantics and domain scoping caveats, materially exceeding annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded with the core purpose, then returns shape, then limitations. It is longer than average, but nearly every phrase carries operational guidance, and the note about non-indexed hosts is important enough to justify its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully specifies the return shape, parameter constraints, domain enum caveats, and integration path to socrata_query. It covers edge cases like USAC E-rate and gives practical querying advice, leaving no critical gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds genuine value: q is clarified as topic-only with jurisdiction moved to domain, including a concrete failure example 'Illinois solicitations' vs 'solicitations'. The domain parameter is enriched with a non-obvious host-to-jurisdiction map and a data ownership caveat for data.colorado.gov.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Find Socrata dataset 4x4 ids by keyword via the Socrata catalog.' It clearly distinguishes the tool's role from siblings like socrata_query and ckan_discover_datasets by mentioning keyless catalog access and the return of dataset IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: feed a result's id to socrata_query as datasetId, and use socrata_query with a known 4x4 for hosts the catalog does not index. This directly addresses when to use this tool versus the natural alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

socrata_discover_datasets

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools