Skip to main content
Glama

Troostwijk Search Lots

troostwijk_search_lots
Read-onlyIdempotent

Browse CURRENTLY-OPEN lots in one Troostwijk Auctions category, European industrial equipment, vehicles, real estate and bankruptcy/insolvency liquidations across NL/DE/BE/UK/PL/RO/IT and more. Returns live current bid, bid count, location and close time per lot. Get category_path from troostwijk_categories first. Bids are served through a 5-minute result cache, so the current bid can be up to five minutes old: near the close of an auction treat it as a lower bound, never as the final price. Sourced from troostwijkauctions.com/en/c/{category_path}.

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": {
      "country": "nl",
      "category_path": "agricultural/tractors/087e1bb8-5fb8-4e98-b5d8-1a0133422ae0"
    },
    "name": "troostwijk_search_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, starting at 1 (each page holds up to 48 lots)
countryNoOptional ISO 3166-1 alpha-2 country code to filter by lot location, e.g. "nl", "de", "be"
category_pathYesCategory path from troostwijk_categories, e.g. "agricultural/tractors/087e1bb8-5fb8-4e98-b5d8-1a0133422ae0"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: it discloses a 5-minute result cache, warns that near auction close the bid should be treated as a lower bound rather than a final price, names the upstream source URL pattern, and lists the per-lot fields returned. With readOnlyHint and idempotentHint already covering the safety profile, this is meaningful added behavioral context an agent could not infer elsewhere.

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?

Purpose is front-loaded in the first clause, followed by return fields, prerequisite, cache caveat, and provenance in descending order of importance. Every sentence carries distinct information; nothing is padding or restatement of the title.

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?

There is no output schema, and the description compensates by naming the returned fields (current bid, bid count, location, close time). Combined with the freshness caveat and the prerequisite call, an agent has everything needed to invoke it correctly and interpret the results.

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 baseline is 3, but the description adds real meaning: it documents where category_path must come from, clarifies that country filters by lot location across a named set of countries ('NL/DE/BE/UK/PL/RO/IT and more'), reinforcing the ISO alpha-2 semantics. The 48-lot page size is duplicated from the schema rather than added.

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?

Names a specific verb and resource ('Browse CURRENTLY-OPEN lots in one Troostwijk Auctions category'), scopes it to open lots only, and enumerates the asset classes and regions covered. The agent can distinguish it from troostwijk_categories (path discovery) and troostwijk_lot_detail (single-lot depth) without opening a 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?

Explicitly states the prerequisite sequence: 'Get category_path from troostwijk_categories first', and limits scope to currently-open lots, which implicitly excludes sold/closed inventory. It stops short of naming troostwijk_sold_comps or troostwijk_lot_detail as alternatives for closed or per-lot data, so routing guidance is clear but not exhaustive.

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.