Housing Intel

Housing Property Report

housing_property_report

Read-onlyIdempotent

Analyze a property by address and zip code. Returns valuation estimate, sales history, tax assessment, and detailed characteristics.

Input Schema

TableJSON Schema

Name	Required	Description
`address1`	Yes	Street address (e.g., "4529 Winona Court")
`address2`	Yes	City, state ZIP (e.g., "Denver, CO 80212")
`_attomKey`	Yes	ATTOM API key (https://api.gateway.attomdata.com)

Output Schema

TableJSON Schema

Name	Required	Description
`address`	No	Full address (address1, address2)
`property`	No
`valuation`	No
`assessment`	No
`sales_history`	No

Schema Changelog

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

Changed13 schema fields changedMay 24, 2026

changedOutput schema / properties / address / description

Previous value: -"Full property address"New value: +"Full address (address1, address2)"

changedOutput schema / properties / assessment / properties / assessed / description
```
Previous value: -"Assessed value"New value: +"Assessed value (USD)"
```
changedOutput schema / properties / assessment / properties / market / description
```
Previous value: -"Market value assessment"New value: +"Market value (USD)"
```
changedOutput schema / properties / assessment / properties / taxAmount / description
```
Previous value: -"Annual tax amount"New value: +"Annual tax amount (USD)"
```
changedOutput schema / properties / property / properties / sqft / description
```
Previous value: -"Square footage"New value: +"Living area in square feet"
```

changedOutput schema / properties / property / properties / yearBuilt / description

Previous value: -"Year property was built"New value: +"Year property was constructed"

changedOutput schema / properties / sales_history / oneOf

Previous value: -[
-  {
-    "items": {
-      "properties": {
-        "amount": {
-          "description": "Sale price",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "type": {
-          "description": "Transaction type",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "properties": {
-      "error": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "items": {
+      "properties": {
+        "amount": {
+          "description": "Sale price (USD)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Sale date",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "description": "Transaction type",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "properties": {
+      "error": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

changedOutput schema / properties / valuation / properties / avm / description

Previous value: -"Automated valuation model estimate"New value: +"Automated valuation model estimate (USD)"

changedOutput schema / properties / valuation / properties / confidence / description

Previous value: -"Confidence score or condition"New value: +"AVM confidence level"

changedOutput schema / properties / valuation / properties / confidence / type

Previous value: -[
-  "string",
-  "number",
-  "null"
-]New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / valuation / properties / high / description

Previous value: -"High end of AVM range"New value: +"High AVM estimate (USD)"

changedOutput schema / properties / valuation / properties / low / description

Previous value: -"Low end of AVM range"New value: +"Low AVM estimate (USD)"

removedOutput schema / required

Removed value: -[
-  "address",
-  "property",
-  "valuation",
-  "sales_history",
-  "assessment"
-]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "description": "Full property address",
+      "type": "string"
+    },
+    "assessment": {
+      "properties": {
+        "assessed": {
+          "description": "Assessed value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "market": {
+          "description": "Market value assessment",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "taxAmount": {
+          "description": "Annual tax amount",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "property": {
+      "properties": {
+        "baths": {
+          "description": "Number of bathrooms",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "beds": {
+          "description": "Number of bedrooms",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "lotSqft": {
+          "description": "Lot size in square feet",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "sqft": {
+          "description": "Square footage",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "yearBuilt": {
+          "description": "Year property was built",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "sales_history": {
+      "oneOf": [
+        {
+          "items": {
+            "properties": {
+              "amount": {
+                "description": "Sale price",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "date": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "type": {
+                "description": "Transaction type",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "properties": {
+            "error": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "valuation": {
+      "properties": {
+        "avm": {
+          "description": "Automated valuation model estimate",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "confidence": {
+          "description": "Confidence score or condition",
+          "type": [
+            "string",
+            "number",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "high": {
+          "description": "High end of AVM range",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "low": {
+          "description": "Low end of AVM range",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "address",
+    "property",
+    "valuation",
+    "sales_history",
+    "assessment"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_attomKey": "your-housing-intel-api-key",
+    "address1": "4529 Winona Court",
+    "address2": "Denver, CO 80212"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety. It adds value by explicitly listing return fields (valuation, sales history, tax assessment, characteristics), which helps the agent understand what to expect.

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 a single, efficient sentence with no extraneous information. Every word earns its place, clearly conveying purpose and outputs.

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?

Given the tool has a small parameter set (3), full schema coverage, and annotations covering safety, the description adequately covers what the tool does and returns. However, it could mention data coverage or limitations (e.g., US only) for completeness.

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% (all parameters have clear descriptions). The description adds that the tool analyzes 'by address and zip code', which is consistent with the schema, but does not provide additional semantic detail beyond what the schema already conveys.

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 the verb 'Analyze' and the resource 'property by address and zip code', and lists specific outputs: valuation estimate, sales history, tax assessment, and detailed characteristics. This distinguishes it from sibling tools like 'housing_market_snapshot' which aggregate market data across properties.

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?

No guidance is provided on when to use this tool versus alternatives such as 'housing_affordability_check' or 'housing_rental_analysis'. No exclusions, prerequisites, or decision criteria are mentioned.

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

All Housing Intel tools Inspect

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.

Housing Property Report

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources