Homechecker Guides

List Homechecker guides

list_guides

Read-onlyIdempotent

List the published Homechecker guide catalogue, optionally filtered by jurisdiction, guide cluster, property type, construction era, or buying stage. Returns metadata only.

Input Schema

TableJSON Schema

Name	Required	Description
`era`	No	For example pre-1920s, 1950s-1970s, or 2000s-on.
`cluster`	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.
`includePillar`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`guides`	Yes
`generatedAt`	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": {
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "generatedAt": {
+      "type": "string"
+    },
+    "guides": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "answer": {
+            "type": "string"
+          },
+          "buyingStages": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "canonicalUrl": {
+            "type": "string"
+          },
+          "cluster": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "blurb": {
+                    "type": "string"
+                  },
+                  "chip": {
+                    "type": "string"
+                  },
+                  "id": {
+                    "type": "string"
+                  },
+                  "label": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "label",
+                  "chip",
+                  "blurb"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "eras": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "jurisdiction": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "limitations": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "propertyTypes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "question": {
+            "type": "string"
+          },
+          "readingTimeMin": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "resourceUri": {
+            "type": "string"
+          },
+          "reviewDue": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "reviewedAt": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topics": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "updatedAt": {
+            "type": "string"
+          },
+          "wordCount": {
+            "anyOf": [
+              {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "question",
+          "summary",
+          "answer",
+          "canonicalUrl",
+          "resourceUri",
+          "jurisdiction",
+          "cluster",
+          "topics",
+          "propertyTypes",
+          "eras",
+          "buyingStages",
+          "updatedAt",
+          "reviewedAt",
+          "reviewDue",
+          "wordCount",
+          "readingTimeMin",
+          "limitations"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "generatedAt",
+    "guides"
+  ],
+  "type": "object"
+}

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 VIC, vic or Victoria."

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the behavioral detail 'Returns metadata only,' which clarifies that full content is not provided. No additional behaviors like pagination or sorting are mentioned, but the annotations lower the bar and this extra detail is valuable.

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 sentence that front-loads the core action and return type, then lists filters. There is no fluff or repetition; every part earns its place.

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 only optional parameters, an output schema exists (so return values are covered), and annotations handle safety, the description is adequate. It states the scope and return type. The only gap is the undocumented includePillar, but that is a parameter semantics issue rather than a completeness issue for the overall tool behavior.

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 67% (5 of 6 parameters have descriptions; includePillar lacks one). The description lists the filter fields but adds no new meaning beyond the schema, and it does not clarify includePillar. With moderate coverage, the description should compensate more but does not.

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 a specific verb ('List') and resource ('published Homechecker guide catalogue'), explicitly notes it returns metadata only, and lists the filter dimensions. This distinguishes it from siblings like get_guide (single guide) and search_guides (likely content search) without ambiguity.

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

Usage Guidelines3/5

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

The description implies usage for browsing the catalogue, but it does not explicitly state when to choose this over search_guides or get_guide. There are no exclusions or alternative references. Usage is inferred from the verb 'List' rather than explicitly guided.

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.