Skip to main content
Glama

govauctions.app

by app.govauctions
OverviewDiscussionsAdmin

Sold-price comps

get_sold_comps
Read-onlyIdempotent

Sold-price comps for a described item, computed across the full government-surplus market in any market listed in country. Signed out: coverage only (how many comparable sales, confidence, and a coarse price band). Signed in or with an API key: the actual 25th/median/75th percentile final prices. liveListingsUrl links to the live auctions for the same item. A miss says which kind it is: reason insufficient_comps (too few comparable sales yet) is worth retrying, reason category_not_priceable (real-estate) never is — that category cannot be priced from a title. A catch-all category such as miscellaneous is not refused: it is dropped and the item is priced on its title alone, with requestedCategory and categoryDropped echoed back — check the resolved category and confidence before trusting the range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesItem description, e.g. '2015 Ford F-150'
limitNoHow many underlying sales to return with include=comps. Capped by plan.
stateNoOptional 2-letter state/region code for a regional range. Falls back to the national range when that state has too few sales; the response's `scope` field says which you got.
countryNoUS
includeNoSet to "comps" to also return the individual sales the range was computed from (title, final price, sale month, state). Requires a key; the number returned is capped by plan. Not served for EU markets (DE, FR, NL, PL): the range is returned with `compsWithheld: true`.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "US",
-  "UK",
-  "CA",
-  "AU"
-]New value: +[
+  "US",
+  "UK",
+  "CA",
+  "AU",
+  "DE"
+]
    • changedInput schema / properties / include / description
      Previous value: -"Set to \"comps\" to also return the individual sales the range was computed from (title, final price, sale month, state). Requires a key; the number returned is capped by plan."New value: +"Set to \"comps\" to also return the individual sales the range was computed from (title, final price, sale month, state). Requires a key; the number returned is capped by plan. Not served for EU markets (DE, FR, NL, PL): the range is returned with `compsWithheld: true`."
  2. Changed2 schema fields changed
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Set to \"comps\" to also return the individual sales the range was computed from (title, final price, sale month, state). Requires a key; the number returned is capped by plan.",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many underlying sales to return with include=comps. Capped by plan.",
+  "type": "integer"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "US"
-]New value: +[
+  "US",
+  "UK",
+  "CA",
+  "AU"
+]
    • addedInput schema / properties / state
      Added value: +{
+  "description": "Optional 2-letter state/region code for a regional range. Falls back to the national range when that state has too few sales; the response's `scope` field says which you got.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses behavior well beyond the annotations: signed-out returns coverage only vs signed-in returns actual percentiles, EU markets return `compsWithheld: true`, miss reasons are typed and actionable, and catch-all categories are dropped with `requestedCategory`/`categoryDropped` echoed back. This is rich, non-obvious operational context.

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?

Dense and front-loaded, leading with the core purpose before the auth-tier and miss-reason detail. It is long, but nearly every sentence carries operational information, so little is wasted.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly, naming `coverage`, `confidence`, price band/percentiles, `liveListingsUrl`, `scope`, `compsWithheld`, `requestedCategory`, and `categoryDropped`. An agent has enough to interpret results correctly.

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?

At 67% schema coverage the description meaningfully supplements the schema: it explains the `include=comps` key requirement and plan cap, EU withholding, and the category-dropping behavior. It adds real meaning but not for every parameter (e.g. `limit`, `state` fallback are already covered by 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?

States a specific verb+resource ('Sold-price comps for a described item') and scope ('full government-surplus market in any market listed in `country`'). It is clearly distinguishable from siblings like get_comp_coverage, get_sold_history, and get_price_trend since it returns a computed percentile range plus a live-listings link.

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?

Gives strong when-to-retry guidance by distinguishing `insufficient_comps` (worth retrying) from `category_not_priceable` (never retry), and explains auth-tier behavior. It lacks an explicit 'use this instead of get_sold_history/get_price_trend' routing statement against named siblings, so it falls short of a 5.

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

All govauctions.app 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