Skip to main content
Glama

Homechecker Guides

by io.github.Steven3265

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
NameRequiredDescriptionDefault
eraNoFor example pre-1920s, 1950s-1970s, or 2000s-on.
clusterNo
buyingStageNoFor example research, contract review, physical inspection, ownership, or selling.
jurisdictionNoAustralia or a state/territory code or name, such as VIC, vic or Victoria.
propertyTypeNoFor example house, apartment, or townhouse or unit.
includePillarNo

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the useful context that it returns only metadata, which aligns with annotations and clarifies the non-destructive, read-only nature.

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 with no wasted words, front-loading the main purpose and listing filters concisely. Every part is essential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema, the description clarifies it returns metadata but doesn't specify what fields are included (e.g., title, ID, description). This leaves some ambiguity for the agent, though the tool is simple enough that it may be acceptable.

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%; the description lists the filter categories (jurisdiction, cluster, property type, era, buying stage) but does not add meaning beyond their names. For example, it doesn't explain what 'buyingStage' values mean or how to format jurisdiction. Baseline of 3 is appropriate.

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 verb 'List' and the resource 'published Homechecker guide catalogue', and distinguishes it from sibling tools like get_guide (single guide) and search_guides (full-text search) by focusing on the catalogue listing with optional filters.

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 guides with filters but does not provide explicit guidance on when to use this tool versus siblings like search_guides or get_guide, nor does it mention when not to use it.

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

All Homechecker Guides toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: list_guides for filtered catalog browsing, search_guides for natural-language queries, get_guide for direct slug-based retrieval, and build_buyer_checklist for constructing a checklist from the corpus. There is no meaningful overlap that would confuse an agent.

Naming Consistency5/5

All tool names follow the same verb_noun pattern: build_buyer_checklist, get_guide, list_guides, search_guides. The verbs are imperative and consistent, making the naming scheme predictable and easy to infer.

Tool Count5/5

Four tools is well-scoped for a guide-focused server. Each tool covers a distinct operation without redundancy, and the count is neither excessively large nor too sparse for the stated purpose.

Completeness5/5

The tool surface fully covers the apparent domain: browsing the catalog (list_guides), searching content (search_guides), retrieving a specific guide (get_guide), and synthesizing guides into a checklist (build_buyer_checklist). No obvious gaps or dead ends exist for typical homebuyer guidance workflows.

Resources