# Georgia Civic Data

> Georgia education, Census, and immigration data: query, filter, aggregate, and link datasets.

- name: org.georgiacivicdata/georgia-civic-data
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 93/100
- quality: 70/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/org.georgiacivicdata%2Fgeorgia-civic-data
- tools: https://api.protogrid.dev/v1/servers/org.georgiacivicdata%2Fgeorgia-civic-data/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "georgia-civic-data": {
      "type": "http",
      "url": "https://mcp.georgiacivicdata.org/mcp/"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% ~updated-44d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 70/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 64 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 5 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_datasets (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_datasets (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query_dataset (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 5,037 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 13, about 5,037 tokens to load them all
- tool set hash: b1ad14ca8e5837ef42da27f02cfc9c19
- tools last changed: 2026-10-19T20:01:40.585Z
- badge: [![protogrid quality](https://protogrid.dev/badge/org.georgiacivicdata/georgia-civic-data.svg)](https://protogrid.dev/servers/org.georgiacivicdata/georgia-civic-data)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `list_datasets` changed (description)
  - before: Enumerate every approved Georgia dataset (topic) and the shared dimensions. Each topic entry is a LEAN summary — name/keys, year coverage (year_min/year_max + year_gaps), detail levels + default detail, a has_demographic flag (false = no demographic axis, so there is no all-students demographic row to filter), tags, contract version, and a one-line description — enough to pick a topic; call describe_dataset for its full schema (columns, filters, grain, source, example queries). Each dimension entry carries its primary key, attribute columns, and (for districts) cross-dataset link keys. Call this first to learn what exists — but for a NAMED task (you already know roughly the topic), prefer search_datasets, which returns far fewer bytes than this full catalog.
  - after: Enumerate every approved Georgia dataset (topic) and the shared dimensions. Each topic entry is a LEAN summary — name/keys, year coverage (year_min/year_max + year_gaps), detail levels + default detail, a has_demographic flag (false = no demographic axis, so there is no all-students demographic row to filter), tags, contract version, and a one-line description — enough to pick a topic; call describe_dataset for its full schema (columns, filters, grain, source, example queries). Each dimension entry carries its primary key, attribute columns, and (for districts) cross-dataset link keys. A top-level `license` object gives the terms the data is served under (CC BY 4.0, with attribution). Call this first to learn what exists — but for a NAMED task (you already know roughly the topic), prefer search_datasets, which returns far fewer bytes than this full catalog.
- 2026-10-13 `lookup_school_zone` added
  - Which Georgia public school attendance zones (elementary, middle, high) contain a place, or (attendance_rules=true) how attendance zones work in Georgia. Give exactly one of: lat + lon; an address (geocoded by the U.S. Census Geocoder); a 2020 census tract_geoid (returns every zone covering the tract with the share of its 2020 population in each, or, when none does, a coverage_reason saying why); or attendance_rules=true with no place. Optional grade (pk, k, 01-12) and year. Returns the district, the zoned schools with labels and provenance (method, accuracy_class, positional_rmse_m, boundary_vintage, currency_status, currency_note, source_url), a level_status per school level, a coverage_status (zoned, gap — some level has no zone there — one_school_per_grade, not_available — the district publishes no zones at some level — with the reason, not_zoned — no zone assigns the grade asked, i.e. pre-K), a currency_warning when a zone's source predates an adopted change that could not be applied (it quotes what changed, by level), an overlap_warning when two schools' zones cover the point for the same grades (it names them, by level), the point's tract and county, and a geojson_url per zone — never the polygons themselves. Zones are reconstructed from published sources of varying currency and are NOT an official enrollment determination: always tell the user to confirm with the district. The zoned school is the default assignment (the result's assignment_note says so). attendance_rules=true returns instead who draws zones and the main ways a student attends a public school other than the zoned one, with the statute or rule behind each: use it when a user asks how zones work or whether a child must attend the zoned school. A dated summary, not legal advice; lang="es" gives it in Spanish.
- 2026-10-13 `resolve_entity` changed (description)
  - before: Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). `kind` is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district' → the school district — they are different things). Fuzzy-matches and ranks candidates, flags `ambiguous` when several tie, and reads only the small dimension table (no fact scan). A real Georgia place is never matched to a different one: a consolidated city returns its county (matched_on=consolidated_city: 'Columbus' -> Muscogee), another city asked as a county returns the county it lies in flagged ambiguous, and a one-letter misspelling returns matched_on=typo. Read `place_note` and tell the user when it is present.
  - after: Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). `kind` is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district' → the school district — they are different things). Fuzzy-matches and ranks candidates, flags `ambiguous` when several tie, and reads only the small dimension table (no fact scan). A real Georgia place is never matched to a different one: a consolidated city returns its county (matched_on=consolidated_city: 'Columbus' -> Muscogee), another city asked as a county returns the county it lies in flagged ambiguous, and a one-letter misspelling returns matched_on=typo. A city school system answers to any common shape of its name (matched_on=city_system: 'Decatur City' / 'Decatur Public Schools' -> City Schools Of Decatur), and a county's system to its place name (matched_on=county_system: 'Gwinnett Public Schools' / 'Cobb Schools' -> the county's district). Read `place_note` and tell the user when it is present.
- 2026-10-13 `aggregate` changed (description)
  - before: Compute a grouped aggregate over one topic — the aggregation-first path. `agg` is one of avg/sum/min/max/count/weighted_rate; `metric` is a metric column (DEFAULTS to the topic key_metric; ignored for count); `group_by` is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). `weighted_rate` computes a true population-weighted SUM(numerator)/SUM(denominator) for a rate key metric (when the contract declares the components) — prefer it over `avg` for a rate across multiple places/years, since `avg` means the per-row rates and ignores population. Supports the same `filters` / `year` / `year_min`-`year_max` / `detail` as query_dataset, plus `order_by`+`order` for top-N (order_by 'value' for the aggregated column; NULL cells sort LAST in either direction). Returns one small row per group with `<metric>_<agg>` (or `row_count`) plus coverage diagnostics (input_rows / non-null counts) so suppression is visible; `aggregation_scope` flags whether rows are source-published at this grain or recomputed from a finer detail (prefer source-published — see the advisory). A `sum`/`weighted_rate` ACROSS a column the contract declares non_additive (overlapping rows, e.g. county rows that count one application in several counties) still returns, but carries a top-level `non_additive` block and a leading `non_additive_sum` advisory: that figure is NOT a total — group_by the column or use the published total row instead. Aggregates SKIP NULLs and NULL means SUPPRESSED not zero. No raw SQL: all identifiers are contract-allowlisted.
  - after: Compute a grouped aggregate over one topic — the aggregation-first path. `agg` is one of avg/sum/min/max/count/weighted_rate; `metric` is a metric column (DEFAULTS to the topic key_metric; ignored for count); `group_by` is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). `weighted_rate` computes a true population-weighted SUM(numerator)/SUM(denominator) for a rate key metric (when the contract declares the components) — prefer it over `avg` for a rate across multiple places/years, since `avg` means the per-row rates and ignores population. With `metric` set to a column the topic's `pooled_rates` lists (a zone's people per square mile), it pools that rate's own declared numerator and denominator (SUM(people) / SUM(land area)) over rows carrying both. Supports the same `filters` / `year` / `year_min`-`year_max` / `detail` as query_dataset, plus `order_by`+`order` for top-N (order_by 'value' for the aggregated column; NULL cells sort LAST in either direction). Returns one small row per group with `<metric>_<agg>` (or `row_count`) plus coverage diagnostics (input_rows / non-null counts) so suppression is visible; `aggregation_scope` flags whether rows are source-published at this grain or recomputed from a finer detail (prefer source-published — see the advisory). A `sum`/`weighted_rate` ACROSS a column the contract declares non_additive (overlapping rows, e.g. county rows that count one application in several counties) still returns, but carries a top-level `non_additive` block and a leading `non_additive_sum` advisory: that figure is NOT a total — group_by the column or use the published total row instead. Aggregates SKIP NULLs and NULL means SUPPRESSED not zero. No raw SQL: all identifiers are contract-allowlisted.
- 2026-10-13 `describe_dataset` changed (description)
  - before: Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection). The top-level `key_metric` names the single headline column most answers want; each column carries `key_metric_grain_contributor` (a grain axis the key metric is only comparable within — pin or group by it) and `metric_component` (numerator/denominator of a rate/average metric). `recommended_query` gives the safe default query shape (key metric + filters to pin + required single-selects) plus a `ranking` recipe for top/bottom-N asks; `filter_hints` lists paired filters; `non_additive` lists columns whose rows overlap (never sum across them; a metric entry names metric columns never to add together) and `value_implications` values that imply another column's value; each categorical filter carries `has_total` / `requires_single_value`. Pass `verbosity='schema'` for a much smaller payload that drops the prose (description/usage/limitations/example queries/column descriptions) but keeps every field needed to compose a correct query — use it when you only need the filter keys and enums; prefer the default 'full' before reporting conclusions (the limitations prose carries the caveats). On an unknown topic returns a self-describing error listing available topics + a 'did you mean' hint. `main_topic` defaults to 'education'; pass 'census' for Census topics or 'immigration' for immigration topics.
  - after: Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection). The top-level `key_metric` names the single headline column most answers want; each column carries `key_metric_grain_contributor` (a grain axis the key metric is only comparable within — pin or group by it) and `metric_component` (numerator/denominator of a rate/average metric). `recommended_query` gives the safe default query shape (key metric + filters to pin + required single-selects) plus a `ranking` recipe for top/bottom-N asks; `filter_hints` lists paired filters; `non_additive` lists columns whose rows overlap (never sum across them; a metric entry names metric columns never to add together) and `value_implications` values that imply another column's value; `year_meaning`, when set, says what `year` labels when it is not when the figures were measured (never present that year as the figures' date); `pooled_rates` lists rates whose figure for several rows is SUM(numerator) / SUM(denominator) (aggregate agg='weighted_rate' with that metric), never an average of the rows' rates; each categorical filter carries `has_total` / `requires_single_value`. Pass `verbosity='schema'` for a much smaller payload that drops the prose (description/usage/limitations/example queries/column descriptions) but keeps every field needed to compose a correct query — use it when you only need the filter keys and enums; prefer the default 'full' before reporting conclusions (the limitations prose carries the caveats). On an unknown topic returns a self-describing error listing available topics + a 'did you mean' hint. `main_topic` defaults to 'education'; pass 'census' for Census topics or 'immigration' for immigration topics.
- 2026-09-27 `aggregate` changed (description)
  - before: Compute a grouped aggregate over one topic — the aggregation-first path. `agg` is one of avg/sum/min/max/count/weighted_rate; `metric` is a metric column (DEFAULTS to the topic key_metric; ignored for count); `group_by` is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). `weighted_rate` computes a true population-weighted SUM(numerator)/SUM(denominator) for a rate key metric (when the contract declares the components) — prefer it over `avg` for a rate across multiple places/years, since `avg` means the per-row rates and ignores population. Supports the same `filters` / `year` / `year_min`-`year_max` / `detail` as query_dataset, plus `order_by`+`order` for top-N (order_by 'value' for the aggregated column; NULL cells sort LAST in either direction). Returns one small row per group with `<metric>_<agg>` (or `row_count`) plus coverage diagnostics (input_rows / non-null counts) so suppression is visible; `aggregation_scope` flags whether rows are source-published at this grain or recomputed from a finer detail (prefer source-published — see the advisory). Aggregates SKIP NULLs and NULL means SUPPRESSED not zero. No raw SQL: all identifiers are contract-allowlisted.
  - after: Compute a grouped aggregate over one topic — the aggregation-first path. `agg` is one of avg/sum/min/max/count/weighted_rate; `metric` is a metric column (DEFAULTS to the topic key_metric; ignored for count); `group_by` is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). `weighted_rate` computes a true population-weighted SUM(numerator)/SUM(denominator) for a rate key metric (when the contract declares the components) — prefer it over `avg` for a rate across multiple places/years, since `avg` means the per-row rates and ignores population. Supports the same `filters` / `year` / `year_min`-`year_max` / `detail` as query_dataset, plus `order_by`+`order` for top-N (order_by 'value' for the aggregated column; NULL cells sort LAST in either direction). Returns one small row per group with `<metric>_<agg>` (or `row_count`) plus coverage diagnostics (input_rows / non-null counts) so suppression is visible; `aggregation_scope` flags whether rows are source-published at this grain or recomputed from a finer detail (prefer source-published — see the advisory). A `sum`/`weighted_rate` ACROSS a column the contract declares non_additive (overlapping rows, e.g. county rows that count one application in several counties) still returns, but carries a top-level `non_additive` block and a leading `non_additive_sum` advisory: that figure is NOT a total — group_by the column or use the published total row instead. Aggregates SKIP NULLs and NULL means SUPPRESSED not zero. No raw SQL: all identifiers are contract-allowlisted.
- 2026-09-27 `describe_dataset` changed (description)
  - before: Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection). The top-level `key_metric` names the single headline column most answers want; each column carries `key_metric_grain_contributor` (a grain axis the key metric is only comparable within — pin or group by it) and `metric_component` (numerator/denominator of a rate/average metric). `recommended_query` gives the safe default query shape (key metric + filters to pin + required single-selects) plus a `ranking` recipe for top/bottom-N asks; `filter_hints` lists paired filters; each categorical filter carries `has_total` / `requires_single_value`. Pass `verbosity='schema'` for a much smaller payload that drops the prose (description/usage/limitations/example queries/column descriptions) but keeps every field needed to compose a correct query — use it when you only need the filter keys and enums; prefer the default 'full' before reporting conclusions (the limitations prose carries the caveats). On an unknown topic returns a self-describing error listing available topics + a 'did you mean' hint. `main_topic` defaults to 'education'; pass 'census' for Census topics or 'immigration' for immigration topics.
  - after: Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection). The top-level `key_metric` names the single headline column most answers want; each column carries `key_metric_grain_contributor` (a grain axis the key metric is only comparable within — pin or group by it) and `metric_component` (numerator/denominator of a rate/average metric). `recommended_query` gives the safe default query shape (key metric + filters to pin + required single-selects) plus a `ranking` recipe for top/bottom-N asks; `filter_hints` lists paired filters; `non_additive` lists columns whose rows overlap (never sum across them; a metric entry names metric columns never to add together) and `value_implications` values that imply another column's value; each categorical filter carries `has_total` / `requires_single_value`. Pass `verbosity='schema'` for a much smaller payload that drops the prose (description/usage/limitations/example queries/column descriptions) but keeps every field needed to compose a correct query — use it when you only need the filter keys and enums; prefer the default 'full' before reporting conclusions (the limitations prose carries the caveats). On an unknown topic returns a self-describing error listing available topics + a 'did you mean' hint. `main_topic` defaults to 'education'; pass 'census' for Census topics or 'immigration' for immigration topics.
- 2026-09-26 `resolve_entity` changed (description)
  - before: Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). `kind` is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district' → the school district — they are different things). Fuzzy-matches and ranks candidates, flags `ambiguous` when several tie, and reads only the small dimension table (no fact scan).
  - after: Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). `kind` is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district' → the school district — they are different things). Fuzzy-matches and ranks candidates, flags `ambiguous` when several tie, and reads only the small dimension table (no fact scan). A real Georgia place is never matched to a different one: a consolidated city returns its county (matched_on=consolidated_city: 'Columbus' -> Muscogee), another city asked as a county returns the county it lies in flagged ambiguous, and a one-letter misspelling returns matched_on=typo. Read `place_note` and tell the user when it is present.

Full history: https://api.protogrid.dev/v1/servers/org.georgiacivicdata%2Fgeorgia-civic-data/changes

## Remotes

- https://mcp.georgiacivicdata.org/mcp/ (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (13)

- `aggregate`: Compute a grouped aggregate over one topic — the aggregation-first path. `agg` is one of avg/sum/min/max/count/weighted_rate; `metric` is a metric column (DEFAULTS to the topic key_metric; ignored for count); `group_by` is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). `weighted_rate` computes a true population-weighted SUM(numerator)/SUM(denominator) for a rate key metric (when the contract declares the components) — prefer it over `avg` for a rate across multiple places/years, since `avg` means the per-row rates and ignores population. With `metric` set to a column the topic's `pooled_rates` lists (a zone's people per square mile), it pools that rate's own declared numerator and denominator (SUM(people) / SUM(land area)) over rows carrying both. Supports the same `filters` / `year` / `year_min`-`year_max` / `detail` as query_dataset, plus `order_by`+`order` for top-N (order_by 'value' for the aggregated column; NULL cells sort LAST in either direction). Returns one small row per group with `<metric>_<agg>` (or `row_count`) plus coverage diagnostics (input_rows / non-null counts) so suppression is visible; `aggregation_scope` flags whether rows are source-published at this grain or recomputed from a finer detail (prefer source-published — see the advisory). A `sum`/`weighted_rate` ACROSS a column the contract declares non_additive (overlapping rows, e.g. county rows that count one application in several counties) still returns, but carries a top-level `non_additive` block and a leading `non_additive_sum` advisory: that figure is NOT a total — group_by the column or use the published total row instead. Aggregates SKIP NULLs and NULL means SUPPRESSED not zero. No raw SQL: all identifiers are contract-allowlisted.
- `describe_dataset`: Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection). The top-level `key_metric` names the single headline column most answers want; each column carries `key_metric_grain_contributor` (a grain axis the key metric is only comparable within — pin or group by it) and `metric_component` (numerator/denominator of a rate/average metric). `recommended_query` gives the safe default query shape (key metric + filters to pin + required single-selects) plus a `ranking` recipe for top/bottom-N asks; `filter_hints` lists paired filters; `non_additive` lists columns whose rows overlap (never sum across them; a metric entry names metric columns never to add together) and `value_implications` values that imply another column's value; `year_meaning`, when set, says what `year` labels when it is not when the figures were measured (never present that year as the figures' date); `pooled_rates` lists rates whose figure for several rows is SUM(numerator) / SUM(denominator) (aggregate agg='weighted_rate' with that metric), never an average of the rows' rates; each categorical filter carries `has_total` / `requires_single_value`. Pass `verbosity='schema'` for a much smaller payload that drops the prose (description/usage/limitations/example queries/column descriptions) but keeps every field needed to compose a correct query — use it when you only need the filter keys and enums; prefer the default 'full' before reporting conclusions (the limitations prose carries the caveats). On an unknown topic returns a self-describing error listing available topics + a 'did you mean' hint. `main_topic` defaults to 'education'; pass 'census' for Census topics or 'immigration' for immigration topics.
- `describe_dimension`: Schema for one dimension (districts / schools / counties / demographics): the (possibly composite) primary key, the attribute columns a join attaches, the cross-dataset `link_keys` (e.g. districts.district_census_id → Census via the crosswalk — a 5-digit school-district code, NOT a county FIPS), and demographics `semantics` (within a category the values are mutually exclusive; `all` is the denominator). Read this before writing a link_query join.
- `distinct_values`: List the distinct values of ONE filterable column of a topic — the fast way to learn valid filter values before query_dataset, especially for FREE categoricals and FK codes (district_code/school_code/county_fips/demographic) that carry no enum in describe_dataset (a wrong guess otherwise returns an empty page with no error). `column` must be a filterable column (see describe_dataset's `filters`). Optional `prefix` does a case-insensitive starts-with filter; `limit` caps results (default 50). Enum-bearing columns return their contract enum directly; others run a capped SELECT DISTINCT over the gold data. `truncated` flags when the list is capped.
- `get_contract`: Return the authoritative ODCS v3.2 data contract for a topic (kind='topic') or a dimension (kind='dimension') so you can consume the machine-readable schema without cloning the repo. fmt='yaml' (default) returns the document verbatim as text; fmt='json' returns it parsed. Only approved topics and loaded dimensions expose a contract.
- `get_dimension`: Paginated read of a dimension table — the label lookups (district names, school names, county names, demographic labels). Rows are ordered by the dimension's primary key so paging is stable. Use describe_dimension for the schema and link keys. Small page defaults; `truncated` + a `bulk_export` pointer signal when to pull the full table elsewhere.
- `link_query`: Run a cross-dataset / cross-topic analytical SQL query that the per-topic query_dataset filters can't express — e.g. join education, Census, or immigration facts to a dimension (or another dataset) on shared geography (immigration and Census county topics share county_fips directly). READ-ONLY, SANDBOXED DuckDB: one SELECT (or WITH … SELECT); no DDL/DML/COPY/ATTACH/INSTALL/PRAGMA/SET/CALL; you may only read_parquet() the curated gold paths returned by link_tables (call it first and paste the snippets) — querying a file path directly is rejected. Joins use the keys from describe_dimension's link_keys (districts.district_census_id bridges to Census via the crosswalk — it is a school-district code, not a county FIPS, so a district is not 1:1 with a county). Results are row- and byte-capped and time-limited; `truncated` flags when capped — add aggregation or a tighter WHERE rather than dumping rows. NULL means suppressed, not zero. On a violation you get a self-describing error naming the offending token/path.
- `link_tables`: List the tables link_query can read (curated gold paths only) and the join keys that bridge facts → dimensions → Census geography. Call this BEFORE writing a link_query. Two-tier to stay context-cheap: with NO arguments it returns a LEAN index — every table's name, grain, detail levels, default `read_parquet(...)` snippet, and join keys (enough to pick tables and write a single-detail join). To get every column and a snippet per detail level for the few tables you actually need, call again with `tables=["<name>", ...]` (a `name` from the index, e.g. 'education/gosa/attendance' or 'attendance', or a dimension like 'districts'). Paste the `read_parquet(...)` snippets verbatim into your SQL — they are exactly what the sandbox accepts.
- `list_datasets`: Enumerate every approved Georgia dataset (topic) and the shared dimensions. Each topic entry is a LEAN summary — name/keys, year coverage (year_min/year_max + year_gaps), detail levels + default detail, a has_demographic flag (false = no demographic axis, so there is no all-students demographic row to filter), tags, contract version, and a one-line description — enough to pick a topic; call describe_dataset for its full schema (columns, filters, grain, source, example queries). Each dimension entry carries its primary key, attribute columns, and (for districts) cross-dataset link keys. A top-level `license` object gives the terms the data is served under (CC BY 4.0, with attribution). Call this first to learn what exists — but for a NAMED task (you already know roughly the topic), prefer search_datasets, which returns far fewer bytes than this full catalog.
- `lookup_school_zone`: Which Georgia public school attendance zones (elementary, middle, high) contain a place, or (attendance_rules=true) how attendance zones work in Georgia. Give exactly one of: lat + lon; an address (geocoded by the U.S. Census Geocoder); a 2020 census tract_geoid (returns every zone covering the tract with the share of its 2020 population in each, or, when none does, a coverage_reason saying why); or attendance_rules=true with no place. Optional grade (pk, k, 01-12) and year. Returns the district, the zoned schools with labels and provenance (method, accuracy_class, positional_rmse_m, boundary_vintage, currency_status, currency_note, source_url), a level_status per school level, a coverage_status (zoned, gap — some level has no zone there — one_school_per_grade, not_available — the district publishes no zones at some level — with the reason, not_zoned — no zone assigns the grade asked, i.e. pre-K), a currency_warning when a zone's source predates an adopted change that could not be applied (it quotes what changed, by level), an overlap_warning when two schools' zones cover the point for the same grades (it names them, by level), the point's tract and county, and a geojson_url per zone — never the polygons themselves. Zones are reconstructed from published sources of varying currency and are NOT an official enrollment determination: always tell the user to confirm with the district. The zoned school is the default assignment (the result's assignment_note says so). attendance_rules=true returns instead who draws zones and the main ways a student attends a public school other than the zoned one, with the statute or rule behind each: use it when a user asks how zones work or whether a child must attend the zoned school. A dated summary, not legal advice; lang="es" gives it in Spanish.
- `query_dataset`: Query one topic's gold facts with dimension labels joined in (the district/school/county/demographic names come back on every row). `filters` is a dict of column → value or list-of-values: FK codes (district_code, school_code, county_fips, demographic) and any categorical column — see describe_dataset's `filters` for the exact keys and enum values. Use `year` (exact) OR `year_min`/`year_max` (range), never both. `detail` picks the grain (default is the finest available). Returns `rows` plus a `columns` descriptor array (type/role/unit/null-meaning, and `is_key_metric` flagging the headline column) so you interpret values and NULLs correctly — NULL usually means SUPPRESSED, not zero (see null_semantics). The top-level `key_metric` echoes which column is the answer. Use `columns` to project a subset, `include_labels=false` to skip the joined name columns (codes only), and `order_by`+`order` for server-side top-N instead of over-fetching. Pages are small (default 100, max 500); when `truncated` is true a `bulk_export` block points at the REST CSV/Parquet endpoint and the source path for the full pull — do not loop pagination to dump a table. A bad filter returns a self-describing error listing the valid keys/values.
- `resolve_entity`: Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). `kind` is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district' → the school district — they are different things). Fuzzy-matches and ranks candidates, flags `ambiguous` when several tie, and reads only the small dimension table (no fact scan). A real Georgia place is never matched to a different one: a consolidated city returns its county (matched_on=consolidated_city: 'Columbus' -> Muscogee), another city asked as a county returns the county it lies in flagged ambiguous, and a one-letter misspelling returns matched_on=typo. A city school system answers to any common shape of its name (matched_on=city_system: 'Decatur City' / 'Decatur Public Schools' -> City Schools Of Decatur), and a county's system to its place name (matched_on=county_system: 'Gwinnett Public Schools' / 'Cobb Schools' -> the county's district). Read `place_note` and tell the user when it is present.
- `search_datasets`: Keyword search over the catalog metadata (topic names, descriptions, tags, AND column names/descriptions) — the discovery entry point when you don't know the exact topic name. Returns lean topic summaries per hit with a relevance score and which fields matched, plus a `dimension_matches` list when the query also hits a dimension (e.g. 'district'). Most acronyms work; the short ones `ap`/`el`/`ib` are recognized. Follow up with describe_dataset. `limit` caps results (default 20, max 100).