Gsa Auctions

Gsa Auctions Closing Soon

gsa_auctions_closing_soon

Read-onlyIdempotent

Current GSA Auctions federal surplus lots that are ending soonest — active auctions sorted by auction end date ascending. Use to find last-chance bidding opportunities across all agencies and property types. Returns sale/lot number, item name, location, end date, status, high bid, and reserve.

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": 25
    },
    "name": "gsa_auctions_closing_soon"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max lots to return (1-200). Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "limit": 25
+  }
+]
```
First observedJul 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint, etc.), the description adds that it returns specific fields (sale/lot number, item name, location, end date, status, high bid, reserve) and is sorted by end date ascending. No contradictions.

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 efficient sentences: first defines what the tool does, second states use case and return fields. No fluff, well front-loaded.

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 simple read-only list tool with one parameter, the description provides all needed context: purpose, sorting, return fields. No output schema exists, but return fields are listed, making it 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 coverage is 100% for the single parameter 'limit', which is well-documented in the schema. The description does not add further semantic meaning about the parameter beyond 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?

The description clearly states it lists GSA auctions ending soonest, sorted by end date ascending, with the specific purpose 'find last-chance bidding opportunities'. This distinguishes it from siblings like 'gsa_auction_lot' (single lot detail) and 'gsa_search_auctions' (search).

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 says 'Use to find last-chance bidding opportunities'. While it doesn't state when not to use, the sibling tool names (gsa_auction_lot, gsa_search_auctions) imply alternatives for other needs.

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

All Gsa Auctions tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.