Skip to main content
Glama

New build buying guides

buying_guides
Read-onlyIdempotent

Use this for how buying a new build home works: reservation, snagging, warranties such as NHBC, part exchange, completion, stamp duty on new builds, mortgages for new builds, leasehold and service charges, and the data-led articles on new build prices. Search by topic to list guides, or give a guide slug for its full text with today's figures filled, its sources and its questions and answers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buying_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoA guide, article or explainer slug a previous call listed.
topicNoWhat the buyer wants to know, in a few words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context. It does add useful return context: full text comes with 'today's figures filled', sources and Q&A, which tells the agent the output is a hydrated document rather than a static article. It says nothing about list-result size, pagination, or what happens when a slug does not match.

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?

Front-loaded with the intent statement, then scope, then the two usage modes in a single trailing sentence. The topic enumeration is long but each item genuinely bounds scope; only the phrase 'how buying a new build home works' is slightly awkward.

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?

With two optional parameters, no output schema and annotations already present, the description covers both invocation paths and sketches the return contents, which is close to complete. The gaps are edge-case behavior (neither or both parameters supplied, unknown slug) and list-result characteristics, which matter because the tool is the entry point to a slug-based flow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the field labels: it explains the mode split (topic returns a list, slug returns full text) and that the slug is one 'a previous call listed', establishing a dependency between the two parameters. Both parameters are optional and the description implies at least one should be supplied, though it does not say what happens if neither or both are given.

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?

A specific purpose statement: 'how buying a new build home works' plus an enumerated topic scope (reservation, snagging, NHBC warranties, part exchange, stamp duty, mortgages, leasehold) makes clear this is an editorial guide library, and the two access modes (topic list vs. slug full text) are named. It does not explicitly say how it differs from calculator siblings such as stamp_duty_calculator or mortgage_calculator, even though it covers those topics as articles, so an agent must infer the boundary.

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?

'Use this for how buying a new build home works' is a clear when-to-use trigger, and the closing clause gives concrete operating guidance for the two modes: search by topic to list, or pass a slug for full text. There are no explicit exclusions telling the agent when to prefer stamp_duty_calculator or new_build_premium instead of these articles.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources