Skip to main content
Glama

Us Auction Events

us_auction_events
Read-onlyIdempotent

Upcoming US auction EVENTS, the sales themselves rather than individual lots ("Synthetic Fuels Company plant liquidation, 271 lots, Aug 28, Fremont CA"). Use this to answer "what auctions are happening near me next week" or "what is this auction house selling". Filter by state, keyword (sale title), auction_house, and a closing date range. Returns each sale with its house, location, lot count, local sale date and a link. Sale dates are the auctioneer's LOCAL calendar date, upstream publishes them without a timezone, so a precise instant is not available at the sale level; individual lot close times (us_auctions_closing_soon) are exact.

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": {
      "limit": 10
    },
    "name": "us_auction_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax sales (1-100, default 25).
stateNo2-letter state code where the sale is held.
keywordNoFree-text matched against the sale title, e.g. "liquidation", "estate", "machine shop".
min_lotsNoOnly sales with at least this many lots, useful for filtering out one-off listings.
closes_afterNoOnly sales closing on or after this date (YYYY-MM-DD). Defaults to today.
auction_houseNoSelling auctioneer, substring match, e.g. "Silicon Valley Disposition".
closes_beforeNoOnly sales closing on or before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / min_lots / description
      Previous value: -"Only sales with at least this many lots — useful for filtering out one-off listings."New value: +"Only sales with at least this many lots, useful for filtering out one-off listings."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's value is the date-semantics warning: sale dates are the auctioneer's local calendar date with no timezone upstream, so no precise instant exists at sale level. It also enumerates the returned fields (house, location, lot count, sale date, link). It stops short of stating pagination or result-count limits, which keeps it below a 5.

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 core definition and the sale-vs-lot distinction before the use-cases and filters. Sentences are dense but each carries information; the timezone caveat is long but necessary. Slightly sprawling for a single paragraph, hence not a 5.

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 7 optional parameters, no output schema, and full annotation coverage, the description supplies what matters: what a result contains, what the date field actually means, and which sibling handles exact lot times. Only result volume/pagination behavior is left unaddressed.

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 every filter is already documented, and the baseline is 3. The description restates the filter set (state, keyword, auction_house, closing date range) and adds only the clarification that keyword matches the sale title — marginal value over 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?

States a specific verb and resource (upcoming US auction events) and immediately disambiguates from lot-level data: 'the sales themselves rather than individual lots', reinforced with a concrete example record shape. An agent can distinguish it from us_auctions_closing_soon and the house/lot tools without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit user-question phrasings it answers ('what auctions are happening near me next week', 'what is this auction house selling'), lists the supported filter dimensions, and names the alternative (us_auctions_closing_soon) for exact lot close times. The 'rather than individual lots' clause functions as a when-not-to-use boundary.

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.