Buy-Box

Score and rank candidates

score_candidates

Read-only

Check a list of listings against a saved buy box and rank them. Pass each listing as an object with whatever fields you scraped (price, mileage, year, seats, a description, etc.).

Numeric rules (max_X, X_max, min_X, X_min) exclude listings that break them.
dealbreakers found in the listing text exclude it.
must_haves, nice_to_haves, preferred_brands_or_models and target_X / X_target score the listing.
Anything the listing doesn't state is 'unknown', not a pass: verify those with the seller's data before recommending. Excluded listings are returned last with the rule they broke. Show the user the ranked results and get confirmation before acting.

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": {
      "category": "<category>",
      "listings": "<listings>"
    },
    "name": "score_candidates"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes
`listings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: numeric rules and dealbreakers exclude listings, unknown values are not treated as passes, excluded listings are returned last with the broken rule, and the user should confirm before acting. This is rich operational context that an agent needs.

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?

The description is front-loaded with the core action and then uses compact bullets for scoring rules. It contains no obvious filler and every section contributes to correct invocation.

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 no output schema, the description still explains exclusion ordering and unknown-value handling, which is strong. It omits what category means and does not say how the saved buy box is obtained, leaving a small completeness gap.

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 0%, and the description compensates well for the listings parameter by explaining that each listing is an arbitrary object with scraped fields. However, the required category parameter is never explained, so semantic coverage is uneven.

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 clearly states a specific action: check listings against a saved buy box and rank them. It is distinguishable from the sibling buy-box CRUD tools, but it does not explicitly name or contrast itself with any sibling.

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 gives clear usage context by explaining how to pass listings and what the scoring rules do. It does not state when not to use the tool or explicitly compare it to alternatives such as get_buy_box or set_buy_box.

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

All Buy-Box 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.