Homechecker Guides
Server Details
Homechecker's professionally authored Australian homebuyer guides: search, cite, build checklists.
- Status
- Healthy
- Uptime
- 100.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Steven3265/homechecker-guides-mcp
- GitHub Stars
- 0
- Server Listing
- Homechecker Guides MCP
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: building a checklist, retrieving a specific guide, listing the catalogue, and searching. No functional overlap exists.
All tool names follow a consistent verb_noun snake_case pattern (build_, get_, list_, search_), making them predictable and readable.
With exactly 4 tools, the set is well-scoped for a guide-management server, covering the essential actions without redundancy or bloat.
The surface covers the full lifecycle: discover (list, search), retrieve (get), and generate (build). No obvious missing operations for the stated domain.
Available Tools
4 toolsbuild_buyer_checklistBuild a Homechecker buyer checklistARead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
|---|---|---|
| checklist | Yes |
TDQS
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.
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.
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.
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.
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.
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.
get_guideGet a Homechecker guideARead-onlyIdempotentInspect
Retrieve one canonical Homechecker guide by slug. Use a slug returned by list_guides or search_guides. Returns source links, review metadata, method and limitations with the guide.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Guide slug, for example reading-a-section-32. Use guides for the main hub. | |
| format | No | full | |
| sectionIds | No | When format is sections, return only these section IDs. |
Output Schema
| Name | Required | Description |
|---|---|---|
| guide | Yes | |
| warning | No | |
| missingSectionIds | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly and idempotent behavior. The description adds transparency about the return content ('source links, review metadata, method and limitations'), which goes beyond the annotations. It does not mention any side effects, but the annotations sufficiently cover that aspect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the purpose and followed by a usage hint and output summary. Every word adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a simple retrieval operation with an output schema provided. The description covers the purpose, usage, and output content sufficiently. No edge cases or error conditions are critical for this simple read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67% with descriptions for slug and sectionIds. The main description enriches slug semantics by tying it to list_guides/search_guides results. The format parameter lacks a description, but its enum values (summary, full, sections) are self-explanatory, and the sectionIds description clarifies the conditional behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Retrieve' with a specific resource ('one canonical Homechecker guide') and its key identifier ('by slug'). It differentiates itself from sibling tools like list_guides and search_guides by emphasizing singularity and canonical status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a direct usage condition: 'Use a slug returned by list_guides or search_guides.' This clearly indicates when to use the tool, though it does not explicitly state when not to use it (e.g., for building checklists) or compare it with build_buyer_checklist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_guidesList Homechecker guidesARead-onlyIdempotentInspect
List the published Homechecker guide catalogue, optionally filtered by jurisdiction, guide cluster, property type, construction era, or buying stage. Returns metadata only.
| Name | Required | Description | Default |
|---|---|---|---|
| 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
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| guides | Yes | |
| generatedAt | Yes |
TDQS
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.
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.
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.
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.
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.
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.
search_guidesSearch Homechecker guidanceARead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| query | Yes | |
| results | Yes | |
| boundary | Yes | |
| matchStrength | Yes |
TDQS
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.
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.
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.
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.
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.
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- Changed
build_buyer_checklist1 field changed- changed
Output 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" +}
- Changed
get_guide1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "guide": { + "anyOf": [ + { + "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" + }, + { + "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" + } + ] + }, + "sections": { + "items": { + "additionalProperties": false, + "properties": { + "heading": { + "type": "string" + }, + "id": { + "type": "string" + }, + "markdown": { + "type": "string" + } + }, + "required": [ + "id", + "heading", + "markdown" + ], + "type": "object" + }, + "type": "array" + }, + "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", + "sections" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "answer": { + "type": "string" + }, + "buyingStages": { + "items": { + "type": "string" + }, + "type": "array" + }, + "canonicalUrl": { + "type": "string" + }, + "checklistCandidates": { + "items": { + "additionalProperties": false, + "properties": { + "section": { + "type": "string" + }, + "text": { + "type": "string" + } + }, + "required": [ + "text", + "section" + ], + "type": "object" + }, + "type": "array" + }, + "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" + } + ] + }, + "contentMarkdown": { + "type": "string" + }, + "eras": { + "items": { + "type": "string" + }, + "type": "array" + }, + "faqs": { + "items": { + "additionalProperties": false, + "properties": { + "answer": { + "type": "string" + }, + "question": { + "type": "string" + } + }, + "required": [ + "question", + "answer" + ], + "type": "object" + }, + "type": "array" + }, + "jurisdiction": { + "items": { + "type": "string" + }, + "type": "array" + }, + "limitations": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "methodology": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "pillar": { + "type": "boolean" + }, + "propertyTypes": { + "items": { + "type": "string" + }, + "type": "array" + }, + "publishedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "question": { + "type": "string" + }, + "readingTimeMin": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "related": { + "items": { + "type": "string" + }, + "type": "array" + }, + "researchNote": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "resourceUri": { + "type": "string" + }, + "reviewDue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "reviewedAt": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "reviewedBy": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ] + }, + "sections": { + "items": { + "additionalProperties": false, + "properties": { + "heading": { + "type": "string" + }, + "id": { + "type": "string" + }, + "markdown": { + "type": "string" + } + }, + "required": [ + "id", + "heading", + "markdown" + ], + "type": "object" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "sources": { + "items": { + "additionalProperties": false, + "properties": { + "accessed": { + "type": "string" + }, + "publisher": { + "type": "string" + }, + "title": { + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "title", + "publisher", + "url", + "accessed" + ], + "type": "object" + }, + "type": "array" + }, + "summary": { + "type": "string" + }, + "title": { + "type": "string" + }, + "topics": { + "items": { + "type": "string" + }, + "type": "array" + }, + "updated": { + "type": "string" + }, + "updatedAt": { + "type": "string" + }, + "wordCount": { + "anyOf": [ + { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "slug", + "pillar", + "resourceUri", + "canonicalUrl", + "question", + "title", + "summary", + "answer", + "updated", + "publishedAt", + "updatedAt", + "reviewedAt", + "reviewDue", + "jurisdiction", + "reviewedBy", + "methodology", + "limitations", + "researchNote", + "wordCount", + "readingTimeMin", + "cluster", + "topics", + "propertyTypes", + "eras", + "buyingStages", + "sections", + "faqs", + "checklistCandidates", + "sources", + "related", + "contentMarkdown" + ], + "type": "object" + } + ] + }, + "missingSectionIds": { + "items": { + "type": "string" + }, + "type": "array" + }, + "warning": { + "type": "string" + } + }, + "required": [ + "guide" + ], + "type": "object" +}
- Changed
list_guides1 field changed- changed
Output 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" +}
- Changed
search_guides1 field changed- changed
Output 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" +}
2 tool updates
- Changed
build_buyer_checklist3 fields changed- changed
Input schema / properties / buyingStage / descriptionPrevious 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." - changed
Input schema / properties / era / descriptionPrevious value: -"For example 1950s-1970s or 2000s-on."New value: +"For example pre-1920s, 1950s-1970s, or 2000s-on." - changed
Input schema / properties / jurisdiction / descriptionPrevious 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."
- Changed
search_guides3 fields changed- added
Input schema / properties / buyingStage / descriptionAdded value: +"For example research, contract review, physical inspection, ownership, or selling." - added
Input schema / properties / era / descriptionAdded value: +"For example pre-1920s, 1950s-1970s, or 2000s-on." - added
Input schema / properties / propertyType / descriptionAdded value: +"For example house, apartment, or townhouse or unit."
4 tool updates
- Changed
build_buyer_checklist2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false
- Changed
get_guide2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false
- Changed
list_guides2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false
- Changed
search_guides2 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / additionalPropertiesRemoved value: -false
3 tool updates
- Changed
build_buyer_checklist1 field changed- changed
Input schema / properties / jurisdiction / descriptionPrevious 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."
- Changed
list_guides1 field changed- changed
Input schema / properties / jurisdiction / descriptionPrevious 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."
- Changed
search_guides1 field changed- changed
Input schema / properties / jurisdiction / descriptionPrevious 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."
4 tool updates
- First observed
build_buyer_checklist - First observed
get_guide - First observed
list_guides - First observed
search_guides
Related MCP Connectors
Search Australian lender credit policies, compare lenders and pre-vet deals, with citations.
Australian mortgage tools: repayment & borrowing-power calculators, guidance & enquiry capture.
Cited, receipt-backed US home-buying data & calculators — education-only, every number sourced.
Real Australian lender serviceability, plus repayments, borrowing power and stamp duty.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI agents to search AustLII (Australian Legal Information Institute) for real Australian legislation and case law. Provides citations with direct links for legal research and verification.-
- AlicenseAqualityAmaintenanceEnables users to search and retrieve Australian legislation and case law with full-text content extraction. Provides structured results with citation metadata and OCR support for archival PDFs.126 npm36Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables natural-language question answering over Australian government policy documents with grounded, source-cited responses and a tool to list indexed documents.-
- AlicenseAqualityCmaintenanceProvides read-only access to over 100 UX/UI design checklists from Checklist.design, enabling users to search and retrieve design guidance for specific flows and screens. Runs locally without an API key.5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.