surplus-auctions-mcp

Compare auctions side by side

compare_auctions

Read-onlyIdempotent

Compare 2–5 GovDeals auctions side by side to see bid, estimated total, end time, and item details, highlighting the cheapest, lowest-mileage, newest, and soonest-ending options.

Instructions

Compare 2–5 GovDeals auctions side by side (bid, estimated total with buyer's premium, end time, location, year, make, model, mileage, hours, condition) and highlight the cheapest, lowest-mileage, newest and soonest-ending. Accepts ids from search results .

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": {
      "auction_ids": "<auction_ids>"
    },
    "name": "compare_auctions"
  }
}

Input Schema

Name	Required	Description	Default
`auction_ids`	Yes	2 to 5 auction ids or URLs to compare

Output Schema

Name	Required	Description	Default
`rows`	Yes
`notes`	Yes
`failed`	Yes
`highlights`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavior beyond that: it discloses the derived 'estimated total with buyer's premium', the ranking highlights performed, and the 2-5 bounds. Missing only error behavior for invalid or expired ids.

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 action, then the compared fields and the highlights in a tight sentence; nothing is padded. The trailing fragment 'Accepts ids from search results .' is slightly clipped and carries a stray space and period, a minor structural blemish.

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 a single well-documented parameter, full annotations, and an output schema, the description needs only to explain scope and what gets computed, which it does. The only real gap is guidance on invalid/expired ids, which is minor for a read-only comparison tool.

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 the single parameter and its accepted formats (search result id or full asset URL) are already fully documented there. The description merely restates the source ('ids from search results') and does not add format or error-handling detail beyond the schema, so baseline 3 applies.

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 gives a specific verb and resource ('Compare ... GovDeals auctions side by side') and enumerates exactly which fields are compared and which winners are highlighted, which no other sibling does. It stops short of naming a sibling to contrast with, though 'Accepts ids from search results' implicitly points at search_auctions as the feeder.

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?

It implies the workflow (call search_auctions first, then pass its ids here) and caps the comparison at 2-5 items, which is useful context. It never says when not to use this versus get_auction_details for a single auction, nor what happens if the ids come from elsewhere.

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

Deploy Server