Skip to main content
Glama

Troostwijk Sold Comps

troostwijk_sold_comps
Read-onlyIdempotent

Realized sale-price comps from Troostwijk Auctions' recently-closed auctions. VERIFIED: closed lots with saleTerm CLOSED_RESERVE_PRICE_ALLOCATED or GUARANTEED_SALE_CLOSED carry a real hammer price in current_bid, and this tool returns ONLY those (outcome:"sold"), reserve-not-met, declined and still-pending lots are filtered out, never reported as a price. Scans recently-closed auctions (bounded by max_auctions) and optionally filters by a keyword in the lot title and/or country. Sourced from troostwijkauctions.com/en/auctions?auctionBiddingStatuses=BIDDING_CLOSED plus each matching auction's lot list.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword to match against lot titles, e.g. "generator", "tractor" (case-insensitive substring; seller-written titles may be in the source country's language)
countryNoOptional ISO 3166-1 alpha-2 country code to filter closed auctions by location, e.g. "nl", "de", "be"
max_auctionsNoHow many recently-closed auctions to scan for sold lots, 1-10 (default 5). Higher finds more matches but costs more upstream requests per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that only verified-sold lots are ever reported as a price, that everything else is filtered out, the upstream pages it scrapes, and the cost tradeoff of raising max_auctions. This is real behavioral context the annotations cannot carry.

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 key scoping fact and organized as verification rule, then scan behavior, then provenance. It is dense and a bit sentence-heavy, but nearly every clause carries information an agent would act on.

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?

For a 3-parameter, zero-required tool with no output schema, it covers what is returned (hammer price in current_bid), what is excluded, how far it scans, and where the data comes from — enough for an agent to call it correctly on the first attempt.

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 100%, so all three parameters are already documented including case-insensitivity, ISO codes and the default of 5. The description only restates that max_auctions bounds the scan and that keyword/country are optional filters, adding little beyond the schema.

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 names a specific verb+resource pair ('Realized sale-price comps from ... recently-closed auctions') and scopes it tightly to verified sold lots, so an agent can distinguish it from a general lot search without opening the schema.

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 states the use case clearly (comps only from lots whose saleTerm is CLOSED_RESERVE_PRICE_ALLOCATED or GUARANTEED_SALE_CLOSED) and explains that reserve-not-met, declined and pending lots are excluded, which implicitly tells the agent to look elsewhere for those. It stops short of naming a specific sibling as the alternative for non-sold data.

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.