Skip to main content
Glama

Us Auctions Closing Soon

us_auctions_closing_soon
Read-onlyIdempotent

US auction lots ordered by soonest close time, the "what can I still bid on before it ends" view across commercial and government sources alike. Optionally filter by state, asset_type, segment, auction_house or keyword. Returns lots with hours remaining, current bid, location and link.

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_auctions_closing_soon"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax lots (1-100, default 25).
stateNo2-letter state code.
sourceNoRestrict to one source.
keywordNoFree-text search over lot title and description.
segmentNogovernment | commercial. Omit for both.
near_zipNoUS 5-digit ZIP to search around, e.g. "94402".
asset_typeNoOne of: vehicle | equipment | realestate | electronics | other.
radius_milesNoRadius around near_zip in miles (1-500, default 50).
auction_houseNoSelling auctioneer, substring match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine value by stating the result ordering and naming returned fields (hours remaining, current bid, location, link), but says nothing about result caps, pagination, or coverage gaps across sources.

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?

Two tight sentences: the identity and ordering come first, filters second, return shape last. Every clause carries information and nothing is repeated from the schema verbatim.

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?

For a read-only, zero-required-parameter list tool with no output schema, the description supplies the ordering, the returned fields, and the filter surface, which is enough to invoke it correctly. Minor gaps remain around the geographic filter pair and result-size behavior, though both are documented in the schema.

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% and all nine parameters are individually documented, so the schema carries the burden. The description only restates five of the filters (state, asset_type, segment, auction_house, keyword) and omits limit, source, near_zip and radius_miles, adding no semantics beyond the schema.

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 resource (US auction lots) and the ordering rule (soonest close time), plus a plain-language gloss of the view ("what can I still bid on before it ends") that makes the intent unmistakable. It does not name a sibling such as us_auctions_search to contrast against, so it falls short of a 5.

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?

The quoted framing sentence gives a clear selection context: use this when the user wants lots with imminent deadlines rather than a general search. It offers no explicit when-not guidance and does not point to alternatives like us_auctions_search for non-deadline queries.

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.