Skip to main content
Glama

Search online property auction lots

search_auction_lots
Read-onlyIdempotent

Search the OpenMoov online property auction catalogue: lots with guide price, starting and current bid, bid count, opening/closing times, the property and the lot page url. Returns available:false when auctions are not currently open to the public. Filter by free text (town, postcode, street, property type) and guide-price range; open_only (default true) hides closed lots. A lot that is no longer open or scheduled shows its street and postcode district only (no house number, no full postcode) and no bid figures. Bidding needs an account, ID checks and a deposit hold, so it is never done in conversation — send the user to the lot url. A guide price is not the reserve.

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": "search_auction_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, max 20
queryNoTown, postcode, street or property type
open_onlyNoDefault true: only lots open or opening for bids
max_guide_priceNoGBP
min_guide_priceNoGBP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses real behavioral traits: available:false when auctions are not open to the public, and that stale or closed lots are anonymised to street plus postcode district with no bid figures. It also flags the account/ID/deposit prerequisite for bidding and warns that a guide price is not the reserve.

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 purpose and returned fields are front-loaded, followed by filtering behaviour and then the important caveats, with no filler sentences. It is dense and slightly long-winded in the anonymisation sentence, but every clause carries operational information.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values and does so explicitly, including the available:false degradation case. For a five-parameter read-only search tool, nothing an agent needs to call it or set user expectations is missing.

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 meaning the schema does not: open_only is framed as hiding closed lots, the query is scoped to town/postcode/street/property type, and the guide-price bounds are given context via the reserve-price caveat.

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 opens with a specific verb and resource ('Search the OpenMoov online property auction catalogue') and enumerates exactly what a lot record contains: guide price, starting/current bid, bid count, opening/closing times, property and lot page url. That level of detail makes it clearly distinguishable from the single-lot sibling get_auction_lot.

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?

It gives concrete when-to-use context: filter by free text (town, postcode, street, property type) and guide-price range, with open_only defaulting to true to hide closed lots, plus an explicit boundary that bidding is never done in conversation and the user must be sent to the lot url. It stops short of naming the sibling to use for full detail on a single lot, so it is clear but not fully routing.

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