Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "time": "2024-Q1"
    },
    "name": "census_homeownership"
  }
}

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (`headline` as a national percent plus rental and homeowner vacancy rates) and the default-to-latest-quarter behavior.

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 sentences, front-loaded with what is returned and from which survey, then the default behavior. Every clause carries information an agent needs, with no redundant restatement of the tool name.

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

Completeness4/5

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

With an output schema present, the description does not need to enumerate return values, yet it usefully summarizes the headline metric. Parameters are fully schema-documented; the only minor omission is guidance on constructing multi-quarter ranges, which the schema example partially covers.

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, and the description only restates the default-to-latest-quarter behavior. It does not explain the range syntax visible in the schema example ("from+2020-Q1+to+2024-Q1"), so it adds no meaning beyond the schema and the baseline of 3 applies.

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

Purpose4/5

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

The description names a specific resource (US homeownership rate and rental/homeowner vacancy rates) and the exact source (Census Housing Vacancy Survey), so an agent can tell it apart from census_housing_starts or census_building_permits by data content. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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 only implied: an agent must infer that this is the tool for headline homeownership/vacancy metrics. There is no explicit when-to-use, when-not-to-use, or named alternative for housing supply questions that belong to census_housing_starts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.