Skip to main content
Glama

Housing Intel

by io.github.pipeworx-io

Housing Mortgage History

housing_mortgage_history
Read-onlyIdempotent

Freddie Mac Primary Mortgage Market Survey — the weekly US mortgage INTEREST rate (the annual percentage borrowers pay on a home loan, e.g. 6.5%), back to 1971. This is the borrowing cost paid by home buyers. Returns the latest snapshot, a time series for the requested window, and min/max/avg stats. Sourced from Freddie Mac directly (not FRED), ingested weekly by the Pipeworx data pipeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoOptional YYYY-MM-DD — returns the rate for the closest observation on or before that date instead of the latest.
windowNo1m | 3m | 6m | 1y | 5y | all (default 1y)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statsNo
latestNo
windowNoTime window requested (1m, 3m, 6m, 1y, 5y, all)
time_seriesNoHistorical mortgage rates in chronological order
as_of_snapshotNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Changed14 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "window": "1y"
+  },
+  {
+    "as_of": "2024-01-15",
+    "window": "5y"
+  }
+]
    • addedOutput schema / properties / as_of_snapshot
      Added value: +{
+  "properties": {
+    "date": {
+      "description": "Closest observation on or before requested as_of date",
+      "type": "string"
+    },
+    "rate_30yr": {
+      "description": "30-year fixed mortgage rate (percent)",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / current_rate
      Removed value: -{
-  "description": "Latest mortgage rate (%)",
-  "type": "number"
-}
    • removedOutput schema / properties / error
      Removed value: -{
-  "description": "Error message if data unavailable",
-  "type": "string"
-}
    • addedOutput schema / properties / latest
      Added value: +{
+  "properties": {
+    "date": {
+      "description": "ISO date of latest observation",
+      "type": "string"
+    },
+    "rate_30yr": {
+      "description": "30-year fixed mortgage rate (percent)",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / note
      Removed value: -{
-  "description": "Data source (Freddie Mac Primary Mortgage Market Survey)",
-  "type": "string"
-}
    • removedOutput schema / properties / snapshot_date
      Removed value: -{
-  "description": "ISO date of latest observation",
-  "type": "string"
-}
    • removedOutput schema / properties / statistics
      Removed value: -{
-  "properties": {
-    "average": {
-      "description": "Average rate in window",
-      "type": "number"
-    },
-    "maximum": {
-      "description": "Max rate in window",
-      "type": "number"
-    },
-    "minimum": {
-      "description": "Min rate in window",
-      "type": "number"
-    },
-    "observations": {
-      "description": "Number of observations in window",
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}
    • addedOutput schema / properties / stats
      Added value: +{
+  "properties": {
+    "avg": {
+      "description": "Average rate in window (percent)",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "max": {
+      "description": "Maximum rate in window (percent)",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "min": {
+      "description": "Minimum rate in window (percent)",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / time_series / description
      Added value: +"Historical mortgage rates in chronological order"
    • changedOutput schema / properties / time_series / items / properties / date / description
      Previous value: -"Observation date (YYYY-MM-DD)"New value: +"ISO date of observation"
    • removedOutput schema / properties / time_series / items / properties / rate
      Removed value: -{
-  "description": "Mortgage rate (%)",
-  "type": "number"
-}
    • addedOutput schema / properties / time_series / items / properties / rate_30yr
      Added value: +{
+  "description": "30-year fixed mortgage rate (percent)",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • removedOutput schema / required
      Removed value: -[
-  "snapshot_date",
-  "window"
-]
  10. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "current_rate": {
+      "description": "Latest mortgage rate (%)",
+      "type": "number"
+    },
+    "error": {
+      "description": "Error message if data unavailable",
+      "type": "string"
+    },
+    "note": {
+      "description": "Data source (Freddie Mac Primary Mortgage Market Survey)",
+      "type": "string"
+    },
+    "snapshot_date": {
+      "description": "ISO date of latest observation",
+      "type": "string"
+    },
+    "statistics": {
+      "properties": {
+        "average": {
+          "description": "Average rate in window",
+          "type": "number"
+        },
+        "maximum": {
+          "description": "Max rate in window",
+          "type": "number"
+        },
+        "minimum": {
+          "description": "Min rate in window",
+          "type": "number"
+        },
+        "observations": {
+          "description": "Number of observations in window",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "time_series": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Observation date (YYYY-MM-DD)",
+            "type": "string"
+          },
+          "rate": {
+            "description": "Mortgage rate (%)",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "window": {
+      "description": "Time window requested (1m, 3m, 6m, 1y, 5y, all)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "snapshot_date",
+    "window"
+  ],
+  "type": "object"
+}
  11. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds context: data sourced directly from Freddie Mac (not FRED), ingested weekly by the Pipeworx data pipeline. This clarifies data freshness and source, going beyond annotations.

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?

The description is 3 sentences with key information front-loaded: data source, frequency, what is returned. No unnecessary words; every sentence adds value.

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?

Given the tool has 2 optional parameters and an output schema (not shown but implied), the description covers source, update frequency, return contents (latest, time series, stats), and data provenance. It is complete for a read-only data retrieval tool.

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%, so the schema already documents both parameters. The description restates their purpose and adds that 'window' defaults to '1y' and 'as_of' returns closest observation. This aligns with baseline 3, as the description adds minor value over schema.

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 clearly states it provides the weekly US mortgage interest rate from Freddie Mac's Primary Mortgage Market Survey, back to 1971. It specifies it returns the latest snapshot, time series, and stats, distinguishing it from sibling tools like housing_market_snapshot or housing_affordability_check.

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

Usage Guidelines4/5

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

The description explains what the tool returns (latest snapshot, time series, stats) and the parameters (window, as_of) but does not explicitly contrast with alternatives. However, the context of mortgage rates vs. other housing metrics is clear, and sibling names help infer usage boundaries.

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

All Housing Intel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools intentionally overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same router, with the beta variant explicitly matching stable behavior right now. entity_profille/recent_changes/compare_entities and the multiple polymarket scanning tools also cover closely related jobs, so an agent must read carefully to avoid picking the wrong variant.

Naming Consistency3/5

All tools use lowercase snake_case, which is a consistent base style. However, the naming grammar is mixed: proper verb_noun tools like compare_entities and validate_claim sit beside noun-phrase/domain tools like housing_market_screen and polymarket_edges, plus the awkward compound case_shiller_metro_compare. The housing_ and polymarket_ prefixes help, but the pattern is not uniform enough for a 5.

Tool Count2/5

41 tools far exceeds the 25+ threshold and the typical well-scoped 3-15 range. Many tools pertyain to Polymarket, npm scanning, llms.txt generation, and memory, which have little to do with Housing Intel, so the count is not earned by the server's stated domain.

Completeness4/5

For the housing domain specifically, the coverage is strong: market snapshot, affordability, employment, mortgage history, rental/property analysis, metro demand, signal scanning, and Case-Shiller comparisons cover the main data needs. The generic ask_pipeworx and deep_research tools also backfill specialized queries. The weakness is scope blur, not obvious missing housing operations.

Resources