General tools · worked recipes

Examples

Open District stays general-purpose: the same MCP tools for every workflow. These are composition patterns — catalog, run_sql, unified_search, list_sources, and entity_path — over the public catalog and data you bring into your tenant. Endpoint: api.opendistrict.org/mcp. A free API key is required (Authorization: Bearer $OD_API_KEY).

Mint a key after signup with scopes data:read, query:run, and vectors:search. See the MCP quickstart.

Patterns

Counterparty screening

Does this legal entity have recent public filings that change our risk read?

Public sources: gleif (gleif.lei-record) · sec-edgar-filings (gov.filing)
Tools: catalog() run_sql(sql) unified_search(query) entity_path(from, to)
How an agent composes it: Call catalog or get_schema to confirm column shapes.

Resolve the counterparty with unified_search or run_sql over gleif.lei-record rows.

Join to gov.filing events on shared identifiers (legal name, CIK, or LEI fields in payload via jsonExtractString).

Optional: entity_path between the LEI entity and a filing entity when names differ.

Dataset pages: GLEIF · company filings (slug sec-edgar-filings).

Vulnerability exposure

Which CVEs on the CISA KEV catalog match software on our asset list?

Public sources: nvd-cves (sec.nvd-cve) · cisa-kev (security.kev)
Your data (BYOD): Upload an asset inventory (product names, versions, or CPE strings) to your tenant via list_sources and connector templates — then join in SQL.
Tools: list_sources() run_sql(sql) unified_search(query, event_type?) entity_path(from, to)
How an agent composes it: list_sources to find your asset table and the public nvd-cves / cisa-kev sources.

run_sql to intersect KEV CVE IDs with NVD detail rows (event_type = 'security.kev' and sec.nvd-cve).

Filter to CVEs that mention products in your BYOD asset list (same SQL session, federated ch_events / events).

entity_path from a product name to a CVE id when graph edges exist.

Related join recipe: NVD × KEV (public catalog only).

Regulatory tracking

What final rules and related bills mention our industry keywords this month?

Public sources: federal-register (gov.document) · congress-bills (gov.bill)
Tools: unified_search(query, event_type?, time_range?) run_sql(sql) catalog()
How an agent composes it: unified_search with event_type: "gov.document" for Federal Register hits on your keywords.

unified_search or run_sql on gov.bill rows from congress-bills (Congress.gov) for legislation in the same topic.

Use run_sql to correlate bill titles or sponsors with rule citations in payload text fields.

Bill data is served from Congress.gov via the congress-bills source (replacing the older govtrack-bills connector). Pages: Federal Register.

Weather alert impact

Which of our sites are under an active NWS warning right now?

Public sources: nws-active-alerts (weather.alert)
Your data (BYOD): Facility or site list uploaded to your tenant (coordinates or counties).
Tools: list_sources() run_sql(sql) unified_search(query, event_type?)
How an agent composes it: run_sql on active weather.alert rows from the public catalog.

Join or filter against your BYOD site table in the same federated query.

unified_search for plain-language questions (“severe thunderstorm warning near Chicago”).

Step-by-step join: NWS alerts × your sites · NWS dataset.

Landing-page scenario cards on the home page use narrative shorthand in examples.yaml; integrate using the ten tools in agents.md only.