Skip to main content
Glama

Housing Intel

by io.github.pipeworx-io

Housing Signal Scan

housing_signal_scan
Read-onlyIdempotent

Scan 45+ housing indicators for anomalies and reversals. Flags unusual moves across rates, starts, sales, prices, wages, unemployment, and rent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_blsKeyNoBLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)
_fredKeyNoFRED API key (gateway-injected; only needed outside the gateway)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
signalsNoDetected anomalies and reversals across housing indicators
scan_dateNoToday's date in YYYY-MM-DD format

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / _blsKey
      Added value: +{
+  "description": "BLS registration key (optional — raises the shared quota; https://data.bls.gov/registrationEngine/)",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_fredKey": "your-housing-intel-api-key"
-  }
-]New value: +[
+  {}
+]
    • changedInput schema / properties / _fredKey / description
      Previous value: -"FRED API key"New value: +"FRED API key (gateway-injected; only needed outside the gateway)"
    • changedInput schema / required
      Previous value: -[
-  "_fredKey"
-]New value: +[]
  3. Changed14 schema fields changed
    • removedOutput schema / properties / error
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / scan_date
      Added value: +{
+  "description": "Today's date in YYYY-MM-DD format",
+  "type": "string"
+}
    • addedOutput schema / properties / signals / description
      Added value: +"Detected anomalies and reversals across housing indicators"
    • removedOutput schema / properties / signals / items / properties / alerts
      Removed value: -{
-  "items": {
-    "properties": {
-      "message": {
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "reversal",
-          "unusual",
-          "accelerating",
-          "turn",
-          "extreme"
-        ],
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / signals / items / properties / current_value
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / signals / items / properties / indicator
      Added value: +{
+  "description": "Name of the housing indicator",
+  "type": "string"
+}
    • removedOutput schema / properties / signals / items / properties / label
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / signals / items / properties / message
      Added value: +{
+  "description": "Human-readable signal description",
+  "type": "string"
+}
    • removedOutput schema / properties / signals / items / properties / series_id
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / signals / items / properties / trend
      Removed value: -{
-  "enum": [
-    "rising",
-    "falling",
-    "stable"
-  ],
-  "type": "string"
-}
    • addedOutput schema / properties / signals / items / properties / type
      Added value: +{
+  "description": "Type of signal detected",
+  "enum": [
+    "reversal",
+    "unusual",
+    "accelerating",
+    "turn",
+    "extreme"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / snapshot_date
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / summary
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / total_signals
      Removed value: -{
-  "type": "number"
-}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "type": "string"
+    },
+    "signals": {
+      "items": {
+        "properties": {
+          "alerts": {
+            "items": {
+              "properties": {
+                "message": {
+                  "type": "string"
+                },
+                "type": {
+                  "enum": [
+                    "reversal",
+                    "unusual",
+                    "accelerating",
+                    "turn",
+                    "extreme"
+                  ],
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "current_value": {
+            "type": "number"
+          },
+          "label": {
+            "type": "string"
+          },
+          "series_id": {
+            "type": "string"
+          },
+          "trend": {
+            "enum": [
+              "rising",
+              "falling",
+              "stable"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "snapshot_date": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "total_signals": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_fredKey": "your-housing-intel-api-key"
+  }
+]
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that the tool scans 45+ indicators and flags unusual moves, but it does not disclose details like data sources, rate limits, or how flags are presented. The added context is mild, so a 3 is appropriate.

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 two concise sentences with no unnecessary words. It front-loads the action ('Scan') and includes a helpful list of covered categories, making it easy to parse.

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?

The tool has zero required parameters and an output schema, so the description can focus on functionality. It lists the indicator categories, giving a good sense of scope. However, it does not mention the data sources or the nature of the anomalies, but this is likely covered by the output schema.

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%, with both parameters (_blsKey and _fredKey) fully described in the schema. The description adds no parameter-specific information, so the baseline of 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?

The description uses a specific verb 'Scan' with a clear resource '45+ housing indicators' and a specific outcome: detecting anomalies and reversals. This distinguishes it from sibling tools like housing_market_snapshot or housing_affordability_check by emphasizing broad anomaly detection across multiple housing categories.

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

Usage Guidelines2/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies a broad screening use case but does not mention any alternative tools, exclusions, or conditions under which another tool would be more appropriate.

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