Homechecker Guides

Search Homechecker guidance

search_guides

Read-onlyIdempotent

Search professionally authored Australian homebuyer guidance using a natural-language question. Use this for general property, inspection, disclosure, apartment, condition, maintenance, era and buying-process questions. It does not assess an actual property.

Input Schema

TableJSON Schema

Name	Required	Description
`era`	No	For example pre-1920s, 1950s-1970s, or 2000s-on.
`limit`	No
`query`	Yes	The homebuyer question or issue to search for.
`cluster`	No
`buyingStage`	No	For example research, contract review, physical inspection, ownership, or selling.
`jurisdiction`	No	Optional state/territory code or name, such as WA, wa or Western Australia.
`propertyType`	No	For example house, apartment, or townhouse or unit.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`results`	Yes
`boundary`	Yes
`matchStrength`	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": {
+    "boundary": {
+      "type": "string"
+    },
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "matchStrength": {
+      "enum": [
+        "none",
+        "weak",
+        "strong"
+      ],
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "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"
+              }
+            ]
+          },
+          "matchedSections": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "heading": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "score": {
+                  "type": "number"
+                },
+                "snippet": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "heading",
+                "snippet",
+                "score"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "matchedTerms": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "propertyTypes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "question": {
+            "type": "string"
+          },
+          "resourceUri": {
+            "type": "string"
+          },
+          "reviewedAt": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "score": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topics": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "question",
+          "summary",
+          "answer",
+          "canonicalUrl",
+          "resourceUri",
+          "jurisdiction",
+          "cluster",
+          "topics",
+          "propertyTypes",
+          "eras",
+          "buyingStages",
+          "updatedAt",
+          "reviewedAt",
+          "limitations",
+          "score",
+          "matchedTerms",
+          "matchedSections"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "matchStrength",
+    "results",
+    "boundary"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedAug 17, 2026

addedInput schema / properties / buyingStage / description

Added value: +"For example research, contract review, physical inspection, ownership, or selling."

addedInput schema / properties / era / description

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

addedInput schema / properties / propertyType / description

Added value: +"For example house, apartment, or townhouse or unit."

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: -"Optional state/territory code such as VIC, NSW or QLD."New value: +"Optional state/territory code or name, such as WA, wa or Western Australia."

First observedJul 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds one behavioral limitation ('It does not assess an actual property') but doesn't discuss return format, pagination, or filtering effects. With annotations covering the core safety traits, the description adds modest extra value.

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 concise sentences with zero redundancy. The primary purpose is front-loaded, and the limitation is stated in a separate short sentence. Every clause 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?

The tool has an output schema, so return values are documented. Parameters are well-described in the schema. The description provides usage context and a key limitation. It could mention that filters like jurisdiction or era refine results, but given the schema's coverage, the description is sufficient for an agent to invoke it correctly.

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 71% and the schema includes descriptions for most parameters (era, query, buyingStage, jurisdiction, propertyType). The description does not mention any parameters, so it adds no extra meaning beyond the schema. Baseline 3 is appropriate given the high schema coverage.

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 states a specific verb ('Search'), resource ('professionally authored Australian homebuyer guidance'), and context ('using a natural-language question'). It enumerates the types of questions it handles, which clarifies scope. However, it doesn't explicitly contrast with sibling tools like get_guide or list_guides, so it relies on sibling names for differentiation.

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 gives explicit 'Use this for...' guidance listing several question categories, and a clear exclusion: 'It does not assess an actual property.' This provides strong context for when to use the tool, but it doesn't mention when to prefer an alternative like get_guide or list_guides, leaving some ambiguity.

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.