Skip to main content
Glama

Census

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Census Homeownership

census_homeownership
Read-onlyIdempotent

US homeownership rate and housing vacancy rates by quarter, from the Census Housing Vacancy Survey (HVS) — the official source. Returns headline (the national homeownership rate as a percent) plus the rental and homeowner vacancy rates. Defaults to the latest published quarter.

Input Schema

NameRequiredDescriptionDefault
timeNoQuarter as "YYYY-QN" (e.g. "2026-Q1"). Defaults to the latest published quarter.
_apiKeyNoCensus API key

Output Schema

NameRequiredDescriptionDefault
timeYesTime period queried
metricYesMetric type
resultsYesArray of homeownership rate records

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-census-api-key",
-    "time": "2024-Q1"
-  },
-  {
-    "_apiKey": "your-census-api-key",
-    "time": "from+2020-Q1+to+2024-Q1"
-  }
-]New value: +[
+  {
+    "time": "2024-Q1"
+  },
+  {
+    "time": "from+2020-Q1+to+2024-Q1"
+  }
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / time / description
      Previous value: -"Time period in YYYY-QN format (e.g., \"2024-Q1\" for Q1 2024). Use \"from+2020-Q1+to+2024-Q1\" for a range."New value: +"Quarter as \"YYYY-QN\" (e.g. \"2026-Q1\"). Defaults to the latest published quarter."
    • removedInput schema / required
      Removed value: -[
-  "time",
-  "_apiKey"
-]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "metric": {
+      "description": "Metric type",
+      "enum": [
+        "homeownership_rate"
+      ],
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of homeownership rate records",
+      "items": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "description": "Homeownership rate data rows",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "time": {
+      "description": "Time period queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "metric",
+    "time",
+    "results"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-census-api-key",
+    "time": "2024-Q1"
+  },
+  {
+    "_apiKey": "your-census-api-key",
+    "time": "from+2020-Q1+to+2024-Q1"
+  }
+]
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description's remaining additions (returned fields, latest-quarter default) largely duplicate the output schema and the time parameter description, adding only the 'official source' trust signal beyond structured data.

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

Conciseness5/5

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

Two compact sentences, front-loaded with the resource and source, with no filler. Every clause carries information an agent needs to decide to call it.

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?

With a full output schema, complete parameter coverage, and rich annotations, the description need not explain return values or safety. It names the dataset, source, and default behavior, which is sufficient for an agent to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in the schema, including the latest-quarter default that the description repeats. The description adds no new syntax, format, or constraint information beyond what the schema provides, so the baseline 3 applies.

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?

States a specific resource (US homeownership and housing vacancy rates), the granularity (by quarter), and the authoritative source (Census Housing Vacancy Survey). This clearly distinguishes it from sibling Census tools like census_acs, census_housing_starts, and census_building_permits, which cover different datasets.

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

Usage Guidelines3/5

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

Usage is implied by naming the exact metric and source, but there is no explicit when-to-use vs. when-not-to-use guidance and no sibling alternatives are named. An agent can infer this is for homeownership/vacancy questions, but must reason about it rather than being told.

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

All Census toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources