Skip to main content
Glama

Live Bring a Trailer auctions, optionally filtered by words

auto_bringatrailer_auctions
Read-only

Live Bring a Trailer auctions (collector cars, motorcycles, parts), optionally filtered by words in the title (e.g. porsche 911) or no-reserve only: title, model year, current bid with currency, auction end time, no-reserve flag, country and listing URL, soonest-ending first, from BaT's public auctions page. 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_bringatrailer_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords that must appear in the title, e.g. porsche 911 (default: all)
limitNoAuctions to return, 1 to 100 (default 20)
noReserveNotrue to list only no-reserve auctions

Output Schema

NameRequiredDescriptionDefault
qNo
countNo
totalNo
sourceNo
auctionsNo
checkedAtNo
liveAuctionsNo
noReserveOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes beyond them with genuinely useful traits: data source (BaT's public auctions page), ordering (soonest-ending first), and a cost model ($0.002 per successful call via x402, failed calls not charged). The one gap is no mention of freshness/refresh cadence for a 'live' feed, but the billing and sorting details are substantial value added.

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 capability and scope, then filters, then returned fields, then sibling routing and price. Dense and mostly waste-free, though the single run-on sentence packs routing and billing into the same block as the core purpose, making it harder to scan.

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 three-optional-parameter read-only listing tool with an output schema and annotations covering safety, the description supplies what those structures cannot: data source, sort order, payment/metering model, and which sibling to use instead. Nothing an agent needs to call it correctly appears to be missing.

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%, so all three parameters are already documented in the schema. The description re-states the two filter concepts and gives an example ('e.g. porsche 911'), which minimally confirms the AND-matching intent, but adds no syntax or edge-case detail beyond the schema (e.g., behavior when q matches nothing, or how limit interacts with the feed).

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?

States a specific resource (live Bring a Trailer auctions) with the domain spelled out (collector cars, motorcycles, parts), the filtering options, the returned fields, and the sort order. It also names the sibling tools (auto_autonation, auto_autotrader) it is not, so an agent can route without opening schemas.

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 routes to alternatives: 'auto_autonation when you need AutoNation cars for sale for a make and optional model' and 'auto_autotrader when you need vehicle listings from AutoTrader.ca: up to 20 per page'. Clear context for choosing among sources, though it never states a when-not-to-use condition for this tool itself (e.g., don't poll for historical sold prices).

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