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

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

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.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. The description still adds real value: 'deterministic' and 'sourced' tell the agent the output is reproducible and groundable to the corpus, and 'assembles general questions and checks' clarifies the output is generic rather than property-specific. It stops short of describing sizing, limits or how parameters shape the result.

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?

Two sentences, zero filler, with the core capability stated first and the negative scope immediately after. Nothing redundant with the title or annotations.

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?

An output schema exists, so return-value detail is unnecessary, and the annotations cover safety. The description covers what the tool does and does not do, but with six optional parameters and no defaults explained, an agent gets no help on how to tailor the checklist or that all inputs are optional.

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 67% (era, buyingStage, jurisdiction, propertyType have descriptions; limit and concerns do not). The description contributes no parameter-level meaning beyond the vague 'buyer context' framing, so it does little to compensate for the coverage gap. With the schema carrying most of the load, a 3 is the appropriate baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and artifact ('Build a deterministic, sourced checklist from the Homechecker guide corpus') plus an explicit scope ('for a buyer context'), so an agent knows exactly what it produces. It clarifies against analysis tools but never positions itself against its actual siblings (get_guide, list_guides, search_guides), so sibling differentiation is missing.

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 positive context ('buyer context') and the explicit exclusion ('does not analyse a listing, document or actual building') tell the agent when this tool is the right one and when it is not. However, it offers no guidance on how it relates to get_guide or search_guides, which are the likely alternative paths to the same corpus.

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.