Skip to main content
Glama
Sign In
Homechecker Guides MCP

Homechecker Guides MCP

by Steven3265
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a Homechecker guide

get_guide
Read-onlyIdempotent

Retrieve a single Homechecker building guide by its slug to access source links, review metadata, methodology, and limitations for Australian residential property inspections.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGuide slug, for example reading-a-section-32. Use guides for the main hub.
formatNofull
sectionIdsNoWhen format is sections, return only these section IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/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, so the safety profile is fully covered by structured data. The description adds the return-value context (source links, review metadata, method, limitations) which is useful. It doesn't address potential behaviors like slug-not-found errors, but with strong annotations, the added context meets baseline expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loaded with the primary purpose, immediately followed by the most critical usage hint (use a slug from sibling tools). It's efficient with no filler, though it could arguably be tightened slightly.

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?

For a read-only retrieval tool with three parameters (one required), strong annotations, and clear schema documentation, the description provides adequate context: what's returned, how to source a slug, and the canonical nature of the guide. With no output schema, describing the return contents is helpful. Minor gaps like error handling aren't critical for this simple fetch tool.

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%, with slug and sectionIds described in the schema. The description adds marginal value by mentioning the guide contains 'method and limitations' but doesn't elaborate on parameter semantics beyond the schema. The slug example and sectionIds behavior are already documented in the schema, so the description adds limited incremental value—baseline 3 is appropriate.

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 clearly states 'Retrieve one canonical Homechecker guide by slug' with a specific verb+resource+method of lookup. It distinguishes itself by noting it retrieves 'source links, review metadata, method and limitations.' However, it doesn't explicitly differentiate from search_guides—though the sibling names imply search vs retrieval, which is somewhat evident.

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 clear guidance to 'Use a slug returned by list_guides or search_guides,' which connects it to sibling tools and provides the correct workflow for obtaining a valid slug. It doesn't explicitly state when NOT to use this tool (e.g., when build_buyer_checklist is appropriate), but the slug-source guidance is practical and helpful.

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

Deploy Server

Other Tools