Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Homes owned free and clear by state

get_state_mortgage_free_homeownership
Read-onlyIdempotent

FreeRateUpdate state dataset: owner-occupied housing units owned free and clear (no mortgage) by state, from the Census ACS 5-year B25081, with the owner-occupied universe, the units with and without a mortgage, the derived share and the ACS vintage, plus the national figure when every state published. A state whose own counts do not reconcile is withheld and named, never returned as a zero. Counts of housing units only: no household, borrower or eligibility inference. Attribution and the canonical page travel with the rows so an answer can be cited.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_state_mortgage_free_homeownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoOptional 2-letter state; omit for every state

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 closed-world, so the bar is lower, yet the description still adds real behavior: a state whose counts do not reconcile is withheld and named rather than returned as zero, and the national figure appears only when every state published. It does not discuss caching, rate limits or row ordering, which keeps it short of a 5.

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?

It is one dense, front-loaded sentence that puts the resource and source first and the caveats after, with no filler. It is slightly run-on, packing five clauses into a single sentence, which costs a point on readability.

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 no output schema, the description carries the return-shape burden and does so: it enumerates the owner-occupied universe, units with and without a mortgage, the derived share, the ACS vintage, the conditional national figure, and the attribution that travels with the rows. Nothing an agent needs to call or cite it is missing.

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 coverage is 100% and the single optional 'state' parameter is fully documented in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the work.

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 names a specific resource (owner-occupied housing units owned free and clear, by state) and its exact provenance (Census ACS 5-year B25081), which is enough to separate it from the other state-level siblings such as get_state_loan_to_income and get_state_property_tax.

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?

It sets a clear scope boundary ('Counts of housing units only: no household, borrower or eligibility inference') and the schema covers the omit-for-all-states case, but it never says when to prefer this over a sibling dataset or what question it answers.

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.

Resources