Skip to main content
Glama

Ritchie Bros. auction calendar: upcoming and running

auto_ritchie_bros_auctioneers
Read-only

Ritchie Bros. (rbauction.com) auction calendar: upcoming and running heavy-equipment, truck and agriculture auctions with name, sale number, start and end time, bidding end, country and city, item count, classification, selling method (timed/live), online bidding, item sites and catalog PDF link. Filter by country code (ISO-3, e.g. USA, CAN, NLD) and limit. From rbauction.com's public auctions page via a residential proxy. Usually takes about 14 s, up to 26 s on slower calls; allow a 45 s timeout. Related tools on this server, for a different need: auto_autonation when you need AutoNation cars for sale for a make and optional model; auto_autotrader when you need vehicle listings from AutoTrader.ca: up to 20 per page. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many auctions, 1 to 100 (default 20), soonest first
countryNoOptional ISO-3 country code of the auction, e.g. USA, CAN, AUS, NLD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses real operational context: residential-proxy sourcing, expected latency (about 14 s, up to 26 s) with a recommended 45 s timeout, and the pricing model ($0.002 per successful call via x402, failures not charged). This is exactly the kind of cost and timing information an agent needs before invoking.

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

Conciseness3/5

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

The core purpose is front-loaded in the first clause, but the long field enumeration duplicates the output schema and the pricing/timeout details are packed into the same run-on block. Every element is relevant, yet the structure makes it harder to scan than a short purpose sentence plus bulleted caveats would.

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?

With an output schema present, the return-field list is redundant but harmless, and the latency, timeout, and payment details round out the operational picture. Only pagination/cursor behavior beyond the numeric limit is left unaddressed, which is minor for a 2-parameter, optional-argument 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 100%, and the description only restates what the schema already says: ISO-3 country codes with examples (USA, CAN, NLD) and a result limit. It adds no meaning about ordering, default behavior, or how filtering interacts with the limit beyond 'soonest first', which the schema already states.

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 names the specific source (Ritchie Bros./rbauction.com), the resource (auction calendar) and the exact scope (upcoming and running heavy-equipment, truck and agriculture auctions), and enumerates the returned fields. It lacks an explicit action verb like 'list' or 'fetch', but the resource is unambiguous.

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 clearly frames this tool as the one for Ritchie Bros. auction data and explicitly redirects to named alternatives for adjacent needs (auto_autonation for AutoNation listings, auto_autotrader for AutoTrader.ca). There are no explicit when-not-to-use conditions, but the routing to siblings is concrete.

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