Skip to main content
Glama
surplus-auctions-mcp

surplus-auctions-mcp

List auctions ending soon

list_ending_soon
Read-onlyIdempotent

Lists government surplus auctions closing within a chosen number of hours, soonest first, so users can find time-sensitive bargains. Filter by state, category, keyword, or maximum bid.

Instructions

List government surplus auctions that close within the next N hours, soonest first — the best time to find bargains. Optionally narrow by state, category, keyword and max price.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hours": "<hours>"
    },
    "name": "list_ending_soon"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYesTime window in hours, e.g. 24 for today, 72 for the next three days
limitNoMaximum results (default 15)
stateNoTwo-letter US state where the item is located, e.g. TX. Omit to search nationwide.
keywordNoOptional keyword, e.g. truck
categoryNoItem category. "vehicles" and "trailers" are filtered natively on GovDeals; other categories are matched by keyword.
max_priceNoOnly auctions whose current bid is at or below this many USD

Output Schema

NameRequiredDescriptionDefault
auctionsYes
warningsYes
total_returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHandle/idempotent/non-destructive/openWorld, so safety is covered. The description adds one genuinely new behavioral fact — results are returned soonest-closing first — but says nothing about pagination, result volume, or what an auction record contains (the output schema handles the latter).

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?

A single sentence that front-loads the core scope and ordering, then lists optional narrowing filters. No redundant or filler wording.

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 rich annotations, a fully documented six-parameter schema, and an output schema, the description supplies everything needed to decide to call it and how results are ordered. Only the absence of explicit sibling routing keeps it from being complete.

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%, including examples for hours, state, and keyword plus the native-vs-keyword category filtering nuance. The description only loosely restates that state/category/keyword/max_price narrow the set and omits hours and limit entirely, adding little 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?

States a specific verb and resource ('List government surplus auctions') plus the defining scope ('close within the next N hours') and result ordering ('soonest first'). That scope distinguishes it from a general search sibling, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The phrase 'the best time to find bargains' implies a use case, and the optional filter list implies a broader search tool exists for other queries, but neither an alternative nor an exclusion is stated. Usage must be inferred from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.