SiteCheck Shop & Social

Copart salvage and used vehicle auctions for a search: lot

social_copart_public_search

Read-only

Copart (US) salvage and used vehicle auctions for a search (make, model, year...): lot number, vehicle title, odometer and its status, title type and state, primary damage, keys, AutoGrade score, yard location, auction timing/status, current bid (USD) and lot link, 20 to 50 lots per search. From copart.com's public search through a rendering residential proxy; buying requires a Copart account. Price: $0.02 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "social_copart_public_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, e.g. 'toyota', 'tesla model 3', '2020 honda civic'

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses use of a rendering residential proxy, the $0.02 USDC charge per successful call, x402 payment networks, and that failed calls are not charged. It also notes the Copart account requirement for buying and the approximate result volume, providing valuable operational and cost 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?

The description front-loads source, scope, and query style, while its proxy, account, and pricing notes are compact and useful. Its first sentence is dense, and the long field inventory likely duplicates the output schema, preventing it from being maximally concise.

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 one-parameter public search with an output schema, this supplies the source, geography, query scope, approximate result volume, account boundary, access mechanism, and exact success/failure pricing. Together with the schema and annotations, it gives the agent enough context to select and invoke the tool correctly.

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?

The sole q parameter is already fully described in the schema, including concrete query examples. The description's 'make, model, year...' wording reinforces suitable query content but adds little new syntax, constraint, or matching behavior beyond that schema, so the high-coverage baseline applies.

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 identifies the resource and scope—Copart's US salvage and used-vehicle auction search—and lists auction-specific results such as lot number, damage, current bid, and yard location. Naming copart.com's public search also distinguishes it from the general marketplace, car-parts, and other auction siblings.

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?

It makes the intended context clear: use a make, model, or year-style query to retrieve Copart auction lots, with 20 to 50 lots per search. It does not explicitly state when not to use it or name an alternative vehicle-search sibling, so it stops short of complete selection guidance.

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

All SiteCheck Shop & Social 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.

Resources

Need Help?