Skip to main content
Glama

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 (how many comparable sales, confidence, a coarse price band) plus categoryStats, the 25th/median/75th percentile of every sale in the item's category (in state when it has enough sales). Signed in or with an API key: the 25th/median/75th percentile for this item itself. 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. pricedAs, when present, is what was actually priced: a spelling fix, or the listing title with its lot count, lot number or serial removed. When the category you sent holds nothing like the item and another category clearly does, the range comes from that one, with requestedCategory and categoryOverridden echoed back. A miss can still carry categoryStats when the item's category is clear, and retryHint when the query was a long listing title: retry with just the brand and model.

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": {
      "q": "<q>"
    },
    "name": "get_sold_comps"
  }
}

Input 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. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "US",
      -  "UK",
      -  "CA",
      -  "AU",
      -  "DE",
      -  "FR"
      -]New value: +[
      +  "US",
      +  "UK",
      +  "CA",
      +  "AU",
      +  "DE",
      +  "FR",
      +  "NL"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "US",
      -  "UK",
      -  "CA",
      -  "AU",
      -  "DE"
      -]New value: +[
      +  "US",
      +  "UK",
      +  "CA",
      +  "AU",
      +  "DE",
      +  "FR"
      +]
  3. 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`."
  4. 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"
      +}
  5. 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"
      +}
  6. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly/idempotent/non-destructive), and the description adds substantial behavioral context beyond that: what is returned when signed out vs signed in vs with an API key, that `compsWithheld` applies to EU markets, the miss-reason taxonomy, and the category-drop/override echo fields. It also warns the agent to check resolved `category` and `confidence` before trusting the range.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, and given the tiered auth behavior plus many response fields with no output schema, most sentences do earn their place. But it is a single unstructured wall of backticked field names with run-on sentences, which costs readability for an agent scanning for a decision.

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 exists, so the description carries the full burden of documenting return values and it does so thoroughly: the percentile band, `categoryStats`, `liveListingsUrl`, miss reasons, and all the echo/resolution fields. An agent has enough to call the tool and interpret both hits and misses 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?

Schema coverage is 67%, and the description meaningfully extends the two least-documented params: `category` (catch-all values are dropped rather than refused, can be overridden, echoed via `requestedCategory`/`categoryDropped`/`categoryOverridden`) and `q` (spelling fixes and title cleanup surface as `pricedAs`). `country` and `state` semantics are largely already in the schema, so the gain is real but partial.

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+resource ('Sold-price comps for a described item') plus the market scope ('full government-surplus market in any market listed in country'). It is clear, but it never names a sibling (get_comp_coverage, get_sold_history, get_sold_comps_batch) to disambiguate this from the other comp-adjacent tools.

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 description does give usage-shaped guidance: retry on `insufficient_comps`, never retry on `category_not_priceable`, and `retryHint` tells you to retry with brand+model for long listing titles. However, it never says when to pick this over siblings like get_sold_history or get_comp_coverage, so tool selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources