Skip to main content
Glama
Sign In

Gsa Auctions

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gsa Search Auctions

gsa_search_auctions
Read-onlyIdempotent

Search current US federal government surplus auctions from GSA Auctions (api.data.gov). GSA Auctions sells government surplus to the public — vehicles, machinery, aircraft, vessels, industrial equipment, electronics, etc. Filter active lots by property state (2-letter, e.g. "TX"), a free-text keyword matched against the item name (e.g. "truck", "forklift", "boat"), and/or auction status. Returns each lot with sale/lot number, item name, property location, sale location, start/end dates, status, high bid, reserve, number of bidders, item and image URLs. NOTE: the upstream API has no server-side category filter — use the keyword argument to narrow by item type.

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,
      "state": "TX",
      "keyword": "truck"
    },
    "name": "gsa_search_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax lots to return (1-200). Default 25.
stateNoFilter by 2-letter property state code (e.g. "TX", "CA"). Matches PropertyState.
statusNoFilter by AuctionStatus (case-insensitive substring, e.g. "Active", "Open"). Omit to include all statuses.
keywordNoFree-text keyword matched (case-insensitive) against the item name — use for category/type (e.g. "truck", "forklift", "aircraft", "boat", "generator").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "truck",
+    "limit": 25,
+    "state": "TX"
+  },
+  {
+    "keyword": "forklift",
+    "limit": 50,
+    "status": "Active"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare it's read-only, idempotent, open-world, and not destructive. The description adds that the upstream API has no server-side category filter, which is critical behavioral context. 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?

Three sentences plus a note, each sentence adds unique value. Front-loaded with purpose and resource. No redundancy or fluff.

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?

No output schema, but the description lists returned fields (sale/lot number, item name, etc.). Covers all parameters and provides examples. Complete for a search tool with no required parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions. The addition adds value: limit default 25, state as 2-letter code, keyword matched against item name, status case-insensitive substring. Examples in the schema further clarify.

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 uses specific verbs and resources: 'Search current US federal government surplus auctions from GSA Auctions'. It clearly distinguishes from siblings like gsa_auction_lot (single lot) and gsa_auctions_closing_soon (subset). The mention of 'api.data.gov' provides context.

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 states filtering by state, keyword, and status. Includes a NOTE about using keyword for category/type due to API limitations. Provides examples in the schema. Lacks explicit when-not-to-use guidance but is clear on context.

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

All Gsa Auctions toolsInspect
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.

Resources