Homechecker Guides

Build a Homechecker buyer checklist

build_buyer_checklist

Read-onlyIdempotent

Build a deterministic, sourced checklist from the Homechecker guide corpus for a buyer context. This assembles general questions and checks; it does not analyse a listing, document or actual building.

Input Schema

TableJSON Schema

Name	Required	Description
`era`	No	For example pre-1920s, 1950s-1970s, or 2000s-on.
`limit`	No
`concerns`	No
`buyingStage`	No	For example research, contract review, physical inspection, ownership, or selling.
`jurisdiction`	No	Australia or a state/territory code or name, such as VIC, vic or Victoria.
`propertyType`	No	For example house, apartment, or townhouse or unit.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`checklist`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "checklist": {
+      "additionalProperties": false,
+      "properties": {
+        "guidanceBoundary": {
+          "type": "string"
+        },
+        "items": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "canonicalUrl": {
+                "type": "string"
+              },
+              "check": {
+                "type": "string"
+              },
+              "guideSlug": {
+                "type": "string"
+              },
+              "guideTitle": {
+                "type": "string"
+              },
+              "section": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "check",
+              "section",
+              "guideSlug",
+              "guideTitle",
+              "canonicalUrl"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "matchedGuides": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "answer": {
+                "type": "string"
+              },
+              "canonicalUrl": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "slug",
+              "title",
+              "canonicalUrl",
+              "answer"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "profile": {
+          "additionalProperties": false,
+          "properties": {
+            "buyingStage": {
+              "type": "string"
+            },
+            "concerns": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "era": {
+              "type": "string"
+            },
+            "jurisdiction": {
+              "type": "string"
+            },
+            "propertyType": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "profile",
+        "guidanceBoundary",
+        "matchedGuides",
+        "items"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "checklist"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedAug 17, 2026

changedInput schema / properties / buyingStage / description

Previous value: -"For example research, before offer or auction, contract review, or physical inspection."New value: +"For example research, contract review, physical inspection, ownership, or selling."

changedInput schema / properties / era / description

Previous value: -"For example 1950s-1970s or 2000s-on."New value: +"For example pre-1920s, 1950s-1970s, or 2000s-on."

changedInput schema / properties / jurisdiction / description

Previous value: -"Australia or a state/territory code or name, such as NSW, nsw or New South Wales."New value: +"Australia or a state/territory code or name, such as VIC, vic or Victoria."

Changed2 schema fields changedJul 30, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedJul 27, 2026

changedInput schema / properties / jurisdiction / description

Previous value: -"Australia or a state/territory code such as VIC, NSW or QLD."New value: +"Australia or a state/territory code or name, such as NSW, nsw or New South Wales."

First observedJul 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, not destructive), the description adds behavioral details: it is 'deterministic' and 'sourced' from a corpus, and it clarifies that it does not analyse actual listings or buildings. This gives the agent a clear understanding of how the tool behaves.

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 concise, consisting of two sentences that are direct and free of fluff. It clearly separates the main purpose from the boundaries, making it easy to parse.

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?

The tool has six optional parameters and an output schema (as indicated by the context), so the description does not need to explain return values or parameter details. It is complete for its purpose, covering what it does and does not do, and the deterministic/sourced attributes give sufficient context for an agent to decide on usage.

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?

The schema already provides descriptions for most parameters (era, buyingStage, jurisdiction, propertyType), but two parameters (limit, concerns) lack descriptions. The tool description does not clarify these or add meaning beyond the schema, so it provides no additional parameter-level guidance.

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 tool's function: building a deterministic, sourced checklist from the Homechecker guide corpus for a buyer context. It also specifies boundaries by noting what it does not do (analyse a listing, document, or building), which distinguishes it from the sibling tools that retrieve guides.

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 implies when to use the tool (when a checklist is needed for a buyer) and explicitly states what it does not do, setting expectations. However, it does not directly reference the sibling tools or provide an explicit 'use this instead of...' guideline, leaving some inference to the agent.

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

All Homechecker Guides tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.